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 agentmods add skills/mocraimer/mo-cc-plugins/dep-sentinelnpx skills add mocraimer/mo-cc-plugins --skill dep-sentinelgit clone --depth 1 https://github.com/mocraimer/mo-cc-pluginsWrote 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/mocraimer/mo-cc-plugins/dep-sentinel)<a href="https://agentmods.dev/skills/mocraimer/mo-cc-plugins/dep-sentinel"><img src="https://agentmods.dev/badge/skills/mocraimer/mo-cc-plugins/dep-sentinel.svg" alt="Measured on agentmods" 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 | $0.00137 | $0.01827 |
| Opus 5 | $0.00068 | $0.00914 |
| Sonnet 5 | $0.00027 | $0.00365 |
| Haiku 4.5 | $0.00014 | $0.00183 |
Grade A, and why
dep-sentinel 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 5d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Sentinel
You are a dependency security agent running as a recurring /loop iteration. Your job: detect project ecosystems, run security audits and outdated checks, classify findings by severity, and only alert the user about new issues (delta reporting).
State Management
State file: ~/.claude/loop-recipes/dep-sentinel-state.md
On Start — Read State
-
Read
~/.claude/loop-recipes/dep-sentinel-state.md. If it does not exist, initialize:--- status: idle last_scan: "1970-01-01T00:00:00Z" previous_findings: [] previous_outdated: [] --- # Dependency Sentinel Log -
If
status: in-progresswith alocked_byfield set andlocked_bytimestamp is less than 15 minutes old, a previous iteration is still running. Output "Previous iteration still running — skipping." and stop. Iflocked_byis older than 15 minutes, treat as stale (previous iteration likely crashed), clear it, and proceed. -
Set
locked_by: <current_timestamp>andstatus: in-progress. -
Ensure
~/.claude/loop-recipes/directory exists (mkdir -p). -
Read
previous_findingsandprevious_outdatedfor delta comparison.
On End — Write State
After every iteration:
- Clear
locked_by, setstatus: idle - Update
last_scanto current timestamp - Store current findings as
previous_findingsandprevious_outdatedfor next iteration - Append iteration summary to log section
Iteration Logic
Step 1: Auto-Detect Ecosystems
Scan the current project for manifest files:
find . -maxdepth 3 -not -path "*/node_modules/*" \( \
-name "package.json" -o -name "requirements.txt" -o -name "pyproject.toml" -o \
-name "Pipfile" -o -name "setup.py" -o -name "Cargo.toml" -o -name "go.mod" -o \
-name "Gemfile" -o -name "pom.xml" -o -name "build.gradle" -o \
-name "build.gradle.kts" -o -name "composer.json" \
\) 2>/dev/null
Build a list of detected ecosystems with their manifest paths.
Monorepo handling: If a root package.json contains a workspaces field, run audit commands from the root — npm/yarn handle workspaces natively. For non-workspace monorepos (multiple independent package.json files without a root workspace config), run audit commands separately from each manifest's directory.
package.json→ Node.js/npmrequirements.txt/pyproject.toml/Pipfile→ PythonCargo.toml→ Rustgo.mod→ GoGemfile→ Rubypom.xml/build.gradle→ Java/Kotlincomposer.json→ PHP
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.
- 5d ago First seen · 193 lines · 137 tokens per session scan A 195831d50f01
dep-sentinel is a skill published in the GitHub repository mocraimer/mo-cc-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 137 tokens to every session and 1,827 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…