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 tdwhere123/do-it --skill do-it-code-qualitygit clone --depth 1 https://github.com/tdwhere123/do-itWrote 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/tdwhere123/do-it/do-it-code-quality)<a href="https://agentmods.dev/skills/tdwhere123/do-it/do-it-code-quality"><img src="https://agentmods.dev/badge/skills/tdwhere123/do-it/do-it-code-quality/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/tdwhere123/do-it/do-it-code-quality"><img src="https://agentmods.dev/badge/skills/tdwhere123/do-it/do-it-code-quality.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.00024 | $0.00300 |
| Opus 5.5 | $0.00010 | $0.00120 |
| Sonnet 5.5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
do-it-code-quality 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 3d 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
Code Quality
Trace the live behavior far enough to find the earliest divergence and the owner of its meaning. A symptom at the UI, cache, or adapter does not establish that layer as the right place for policy.
Useful questions include whether a legitimate mutation can bypass a check, and whether a rule would survive replacement of the layer that currently implements it. Map both producers and consumers when changing an API, schema, or boundary.
Prefer a direct durable change. Before adding a mechanism, look for an existing one, including near-copies left by earlier sessions. Prepare structure only when the current shape blocks the change or its verification. Include required contract fallout; nearby cleanup earns its place through the problem being solved.
For stateful work, consider applicable identity, interleaving, commit, retry, and copied-state failures. The stateful scan and causal change notes offer deeper prompts. A regression should observe the changed contract with an expectation independent of the implementation; use a focused probe when that is more informative.
An independent mapper or specialist can expose a mistaken causal model. Pass source facts and label your interpretation as a hypothesis. See delegation.
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.
- 3d ago Changed · +1 lines ab5773573dbb
- 1mo ago Changed · -60 lines · -17 tokens per session 131bceb3b8a7
- 1mo ago Changed · -20 lines · -1 tokens per session a1e4ba516e01
- 1mo ago First seen · 109 lines · 42 tokens per session scan A e4dda099d9ed
do-it-code-quality is a skill published in the GitHub repository tdwhere123/do-it (28 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 300 once invoked, about $0.0001 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
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.
rn-debugging
This skill should be used when the user asks to "debug the app", "fix a crash", "diagnose a blank screen", "read error logs", "troubleshoot CDP connection", "check Metro status", "find native crashes", "inspect network failures", "the app crashed", "I see a blank screen", "the screen is white", "something broke", "app…
dpf-evidence-before-diagnosis
Use when about to claim a cause for a DPF symptom without having checked the live DB, status fields, logs, or runtime state.
dpf-systematic-debugging
Use when a DPF symptom needs a root cause — a failing build, a wedged runtime, a stuck job, wrong output.
dpf-blast-radius
Use before shipping a DPF change to find what it breaks elsewhere — a refactor, renamed field, contract/schema/enum edit, shared helper, or a diff you do not trust.
estate-divergence-classification
Classify estate divergences with evidence.