scaffold-cost-check
SolidMeasure 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.
Install
Quality Score: 86/100
Skill Content
Details
- Author
- haabe
- Repository
- haabe/mycelium
- Created
- 3 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
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
canvas-health
Lint canvas files for staleness, missing fields, inconsistent evidence types, and orphaned references. Run periodically or before major transitions.
scaffold
Drive @mohantn/scaffold-core for deterministic boilerplate scaffolding (DTOs, endpoints, services, route registration, frontend API clients) from a configured template pack when the user's request splits into "boilerplate the CLI can render" + "logic only the user can describe." Use when the user is adding or extending a new file/resource/service that follows an existing target-stack pattern. Skip when the task is mostly modifying existing implementations, or is fully bespoke code with no target-stack boilerplate to render.