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/postrv/narsil-mcpWrote 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/postrv/narsil-mcp/supply-chain)<a href="https://agentmods.dev/commands/postrv/narsil-mcp/supply-chain"><img src="https://agentmods.dev/badge/commands/postrv/narsil-mcp/supply-chain/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/postrv/narsil-mcp/supply-chain"><img src="https://agentmods.dev/badge/commands/postrv/narsil-mcp/supply-chain.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.00011 | $0.00274 |
| Opus 5 | $0.00005 | $0.00137 |
| Sonnet 5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
supply-chain 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.
What it actually says
Supply Chain Analysis
Perform a comprehensive supply chain security analysis on a repository.
Workflow
-
Identify repository: If $ARGUMENTS is provided, use it as the repo name. Otherwise, use
list_reposand ask which one to analyze. -
Generate SBOM: Use
generate_sbomwithformat="cyclonedx"to create a software bill of materials -
Check for vulnerabilities: Use
check_dependencieswithinclude_dev=trueandseverity_threshold="low"to find all known CVEs -
Find upgrade paths: Use
find_upgrade_pathto identify safe upgrades for vulnerable dependencies -
Check license compliance: Use
check_licensesto identify license issues. If the user specifies a project license, pass it viaproject_license. -
Summarize findings:
- Total dependencies (direct and transitive)
- Vulnerable dependencies with severity breakdown
- Available safe upgrades
- License compatibility issues
- Recommended actions prioritized by risk
Arguments
Repository to analyze: $ARGUMENTS
Example usage:
/narsil:supply-chain/narsil:supply-chain myproject
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 · 35 lines · 11 tokens per session scan A 76b61af8afaf
supply-chain is a command published in the GitHub repository postrv/narsil-mcp (182 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 274 once invoked, about $0.0001 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 commands, from other repositories
localnest:remember
Save a decision, fact, or learning to LocalNest memory.
localnest:fact
Add a structured fact to the knowledge graph.
localnest:ingest
Ingest a conversation file into memory and knowledge graph.
localnest:onboard
Run the guided first-run setup wizard that configures everything automatically.
localnest:recall
Recall relevant memories for the current task or query.
localnest:search
Search codebase and memory via LocalNest.