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 alirezarezvani/ClaudeForge --skill claude-md-dependency-rescangit clone --depth 1 https://github.com/alirezarezvani/ClaudeForgeWrote 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/alirezarezvani/claudeforge/claude-md-dependency-rescan)<a href="https://agentmods.dev/skills/alirezarezvani/claudeforge/claude-md-dependency-rescan"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claudeforge/claude-md-dependency-rescan/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/alirezarezvani/claudeforge/claude-md-dependency-rescan"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claudeforge/claude-md-dependency-rescan.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.00062 | $0.00653 |
| Opus 5 | $0.00031 | $0.00327 |
| Sonnet 5 | $0.00012 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
claude-md-dependency-rescan 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 10d 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
CLAUDE.md Dependency Rescan (forked, read-only)
Optional explicit manifest: $ARGUMENTS (default: auto-detect all five manifest types).
Run these steps in order. Do not modify any file.
- Detect manifests. Look for
package.json,requirements.txt,pyproject.toml,go.mod,Cargo.tomlat the repo root and one level deep (workspaces/monorepos). - Extract declared dependencies from each:
package.json→ keys ofdependenciesanddevDependencies(skip versions).requirements.txt→ first token of each non-comment line.pyproject.toml→[project.dependencies]/[tool.poetry.dependencies]keys.go.mod→ module paths underrequire (...).Cargo.toml→ keys under[dependencies]/[dev-dependencies].
- Inventory documented deps in every
CLAUDE.md(and.claude/rules/*.md): grep for the Tech Stack / Dependencies sections and the lists under them. - Compute three sets per file:
added: in manifest but absent from this CLAUDE.md.removed: documented in this CLAUDE.md but absent from manifest.renamed: documented and present in manifest but spelled differently (react-routervsreact-router-dom,pgvspsycopg2).
- Return in this exact shape:
## Dependency Rescan
Manifests detected: <list>
Total declared deps: <count>
### Per file
#### <path-to-CLAUDE.md>
- Added (in manifest, not documented): <list or "none">
- Removed (documented, not in manifest): <list or "none">
- Renamed / aliased: <list or "none">
- If every documented set matches its manifest, return exactly
## Dependency Rescan\n\nAll documented deps match manifests. <M> files inspected.. Do not pad.
Hard rule: do not propose specific edits — just surface the diffs. /sync-claude-md decides whether to write them.
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.
- 10d ago First seen · 55 lines · 62 tokens per session scan A 7280eaaadcbd
claude-md-dependency-rescan is a skill published in the GitHub repository alirezarezvani/ClaudeForge (424 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 653 once invoked, about $0.0003 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-30.
Other skills, from other repositories
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
langsmith-tracing
LangSmith tracing and debugging setup for LLM applications. Configure observability, capture traces, and enable debugging for LangChain/LangGraph agents.
moai-workflow-ddd
Domain-Driven Development workflow specialist using ANALYZE-PRESERVE-IMPROVE cycle for behavior-preserving code transformation. Use when refactoring legacy code or reducing technical debt safely.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
moai-workflow-loop
Ralph Engine - Automated feedback loop with LSP diagnostics and AST-grep integration for continuous code quality improvement. Use when implementing error-driven development, automated fixing, or continuous quality validation workflows.