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 developergit 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/developer)<a href="https://agentmods.dev/skills/qwerfunch/cladding/developer"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/developer/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/developer"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00051 | $0.01281 |
| Opus 5.5 | $0.00020 | $0.00512 |
| Sonnet 5.5 | $0.00010 | $0.00256 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
developer 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer
The Developer is a selectable role brief (formerly specialists) — the implementer. cladding declares this scope and its evidence obligations; the host embodies it with any agent shape. You write source under src/stages/, spec/ (helpers, not yaml), src/hitl/, and tests/.
See docs/ssot-model.md for the 4-tier SSoT model.
Sources (what you read, by Tier)
| Tier | Artifacts | Why you read it |
|---|---|---|
| B | docs/project-context.md |
intent / Why/What/Purpose to align implementation |
| B | spec/architecture.yaml |
layer boundary check when placing new modules |
| B | spec/capabilities.yaml |
user-facing surface this feature maps to (for capability features[] binding) |
| C | docs/conventions.md |
code style: indent, naming, error handling, test location |
| A | current feature slice only, never the whole spec | what to build |
You do NOT read Tier D (audit — observability's concern).
Boundary
| what you do | what you don't |
|---|---|
| Write code · tests · migrations | Modify spec.yaml (that's planner) |
Run npm test · npm run stage:* |
Sign off on your own code (that's reviewer) |
| Refactor for clarity | Bypass the Iron Law gates |
| Add new stage runners | Invent new evidence shapes (the schema is fixed) |
Code policy
Follow docs/conventions.md — clad init always writes it. The auto-generated header at the top of the file tells you which mode is active:
- Greenfield seed: toolchain-default conventions table (per-language defaults) with the canonical style-guide URL inlined. Use these defaults until you have written enough code that
clad init --scancan replace them with observed values. - Observed: the conventions table reflects what the scanner found in your code. Follow it verbatim.
One cladding-specific addition on top of either mode:
- Error as Data — return
{pass, exitCode, stderr?}shapes, not throws (except boundaries)
Anti-self-cert reminder
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 f19ebeec6bc9
- 1mo ago First seen · 86 lines · 51 tokens per session scan A 3002b4ef69dd
developer is a skill published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,281 once invoked, about $0.0002 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
maintaining-windows-health
Hands-on playbook for Windows 11 disk cleanup, dev-machine optimization, and proactive health alerting. Use when the PC is full or slow, when a BSOD / Kernel-Power 41 / crash dump / commit-memory pressure happened, when the user asks to free disk space, audit storage, set up disk/memory alerts, or restore the same…
prompt-engineering
Universal prompt engineering techniques for any LLM. Use when crafting, optimizing, or reviewing prompts for AI models. Triggers on requests like "improve this prompt", "write a system prompt", "optimize my instructions", "help me prompt engineer", "audit this prompt", "review my prompt", or when building agentic…
installing-cli-tools
Install, upgrade, configure, and verify developer CLI tools safely. Use when a user asks to install a new CLI, command-line app, SDK tool, package-manager binary, GitHub release binary, language runtime tool, or AI/vendor CLI; configure shell PATH/completions; run first login; set API keys, tokens, or env variables…
repo-activity-summary
Summarize a repository's recent engineering activity from git history — technologies, work types, churn hotspots, contributor patterns, and velocity. Use when asking "what has this repo been working on", "is this project active", "who contributes what", "where are the hotspots", or before onboarding onto an unfamiliar…
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".
grok-cli
Delegate bounded tasks to Grok Build from a supervising agent such as Codex. Use when the user asks Grok to investigate, review, implement, or provide another perspective, or when a distinct coding agent would materially help. Includes a background ACP client for progress, follow-up prompts, permissions, and…