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.
git clone --depth 1 https://github.com/shamimfahad/adlc-toolkitWrote 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/commands/shamimfahad/adlc-toolkit/recover)<a href="https://agentmods.dev/commands/shamimfahad/adlc-toolkit/recover"><img src="https://agentmods.dev/badge/commands/shamimfahad/adlc-toolkit/recover/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/commands/shamimfahad/adlc-toolkit/recover"><img src="https://agentmods.dev/badge/commands/shamimfahad/adlc-toolkit/recover.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.00076 | $0.00356 |
| Opus 5 | $0.00038 | $0.00178 |
| Sonnet 5 | $0.00015 | $0.00071 |
| Haiku 4.5 | $0.00008 | $0.00036 |
Grade A, and why
recover 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 9d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 9d ago First seen · 14 lines · 76 tokens per session scan A 22f052c6d1ac
recover is a command published in the GitHub repository shamimfahad/adlc-toolkit (5 stars, last pushed 27d ago), with no licence file. It adds 76 tokens to every session and 356 once invoked, about $0.0004 per session on Opus 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-31.
Other commands, from other repositories
smart-fix
Command "smart-fix" from HermeticOrmus/LibreUIUX-Claude-Code, covering intelligent issue resolution with multi-agent orchestration, phase 2: root cause investigation - deep code analysis, multi-domain coordination for complex issues, configuration options and modern debugging tools integration.
Diagnose
Run a 20-point health check across the plugin install, project config, PM/notification reachability, docs freshness, board consistency, and git state. Read-only — never changes state. Reports each check as PASS/WARN/FAIL/SKIP with an actionable fix. Target under 15 seconds end-to-end. Use before demos, after a plugin…
smart-fix
Command "smart-fix" from HermeticOrmus/claude-code-game-development, covering intelligent issue resolution with multi-agent orchestration, phase 2: root cause investigation - deep code analysis, multi-domain coordination for complex issues, configuration options and modern debugging tools integration.
debug
Diagnose Ansible playbook issues from symptoms.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.