scaffold-cost-check

Solid

Measure Mycelium's own scaffold token cost (CLAUDE.md + engine + harness + canvas + memory) and surface a structured estimate. One-shot audit; pair with /framework-health for trend tracking.

AI & Automation 45 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
55
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Scaffold Cost Check Measure the token cost of Mycelium's stable scaffolding — the context surface loaded at SessionStart and on routine canvas/memory reads — so claims about "negligible overhead" are auditable. Datadog's *State of AI Engineering* (2026) reports ~69% of input tokens across production agents are system prompts; this skill makes Mycelium's analogous number visible. ## When to Use - First-time audit on a project to compare actual scaffold cost against any "~6K negligible" claim in landscape/positioning. - Periodic refresh via `/mycelium:framework-health` (see Wiring below). - Before adding a new canvas file or harness doc that joins the stable load surface, to surface the marginal cost. ## Preflight: Read target canvas file(s) before any Write/Edit Hard rule. Before issuing `Write` or `Edit` against any `.claude/canvas/*.yml`, use the **Read tool** on that file in this session. This skill only WRITES if explicitly asked to persist its output to `dora-metrics.yml#apex.scaffold_token_estimate`; default behavior is print-only. ## Workflow 1. **Inventory the stable scaffold surfaces** in the current project's plugin cache (or fall back to `.claude/` for legacy installs): - `CLAUDE.md` (project-local; the dispatcher) - `${CLAUDE_PLUGIN_ROOT}/engine/` (all `.md` and `.yml`) - `${CLAUDE_PLUGIN_ROOT}/harness/` (all `.md`) - `AGENTS.md` (project-local, if present — the router for non-Claude-Code runtimes; **not** a plugin file. It lives at a repo root...

Details

Author
haabe
Repository
haabe/mycelium
Created
5 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

harness-audit

Audits a Claude Code setup end-to-end: what loads every session, what it costs, and whether the harness's own claims hold. Inventories the standing surfaces (CLAUDE.md chain, personal/project/plugin skills, MCP instruction blocks, agent rosters, hooks, settings at every scope), quantifies their per-session token cost, runs five checks (self-consistency, duplication across scopes, enforcement parity, scope discipline, and a provisional routing-effectiveness check for doc-fleet repos) and reads the CLAUDE.md chain as intent (code outranks the doc; no restated stack, deps, or layout). Output is a quantified triage that stays in-repo: findings at machine scope (anything under ~/.claude, user or enterprise settings, global plugins) are reported for the owner to action, never edited. Use to review, slim, or sanity-check a whole Claude Code setup (including 'why is my context so big' or 'what loads every session') after major harness changes (a new plugin fleet, a new machine, a model release) or when sessions feel

3 Updated 1 months ago
claudialnathan
AI & Automation Listed

project-scaffolding

This skill should be used when the user wants to set up Claude for a project, create a CLAUDE.md file, scaffold the .claude directory, initialize an AI workflow, configure a project for Claude, set up dev intelligence, initialize a new project, or do a new project setup. Triggered by phrases like "set up claude for this project", "create CLAUDE.md", "scaffold .claude directory", "init AI workflow", "configure project for claude", "set up dev intelligence", "initialize project", "new project setup".

0 Updated 1 months ago
nickthelegend
AI & Automation Listed

dhpk-harness-budget

Audits Claude Code context-window token consumption across agents, skills, MCP, rules, and CLAUDE.md; produces prioritized token-savings fixes. Use when: context feels bloated, after adding components, or checking headroom. Not for: trimming harness structure (use dhpk-harness-revise), backfilling .claude/ (use dhpk-harness-fill), or checking hook/plugin health (use dhpk-claude-health). Output: budget report + ranked fixes.

2 Updated today
hmj1026