Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add qwerfunch/cladding --skill statusgit clone --depth 1 https://github.com/qwerfunch/claddingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/qwerfunch/cladding/status)<a href="https://agentmods.dev/skills/qwerfunch/cladding/status"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/qwerfunch/cladding/status"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00076 | $0.00216 |
| Opus 5.5 | $0.00030 | $0.00086 |
| Sonnet 5.5 | $0.00015 | $0.00043 |
| Haiku 4.5 | $0.00008 | $0.00022 |
Grade A, and why
status scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Cladding status (formerly panel)
Run clad status from the project root. Renders an ASCII matrix:
- Rows: features (business titles by default; raw ids with
--internal— legacyF-NNNfor historical features, and current generatedF-<hash8>identifiers). - Columns: 15 Iron Law stages.
- Cells: pass · skip · fail · not-yet-attempted.
Use this after clad check to see which features failed which stages at a glance, not just the aggregate exit code.
clad status
clad status --internal
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed 32e07ed16eac
- 1mo ago First seen · 19 lines · 76 tokens per session scan A 09faadc50b34
status is a skill published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 216 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
report
Activity report from total-agent-memory for a project and period. Use when the user types /report or asks "report for today", "what did we do this week", "weekly / monthly summary", "status report", "retro for project X", "all-time report", "report for last week", or a report for a department or the whole company on…
retro
Engineering retrospective from git metrics. Reports deployment frequency, release cycle span, churn hotspots, backlog health. Outputs narrative report with 3+ actionable items. Flags: --since, --path, explicit range argument.
backlog
Manage the project's tech debt backlog. Add, list, fix, wontfix, delete, prioritize, and suggest batch actions on tracked issues. Used by audit and review skills to persist findings, and directly by users to manage accumulated debt. Modes: list [category], add [description], fix B-{N}, wontfix B-{N} [reason], delete…
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…