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/plugins/postrv/narsil-mcp/narsil-plugin)<a href="https://agentmods.dev/plugins/postrv/narsil-mcp/narsil-plugin"><img src="https://agentmods.dev/badge/plugins/postrv/narsil-mcp/narsil-plugin/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/plugins/postrv/narsil-mcp/narsil-plugin"><img src="https://agentmods.dev/badge/plugins/postrv/narsil-mcp/narsil-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
narsil 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 1mo 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
{
"name": "narsil",
"description": "Code intelligence plugin for narsil-mcp. Provides guidance for using 90 code analysis tools including security scanning, call graph analysis, symbol search, supply-chain SBOM, and SPARQL/CCG knowledge graph export.",
"version": "1.0.0",
"author": {
"name": "Laurence"
},
"homepage": "https://github.com/postrv/narsil-mcp",
"repository": "https://github.com/postrv/narsil-mcp",
"license": "MIT OR Apache-2.0",
"keywords": [
"code-intelligence",
"security",
"static-analysis",
"call-graph",
"supply-chain",
"sbom",
"sparql",
"knowledge-graph",
"mcp"
]
}
What it installs
The manifest is a name and a version. 1 skill, 5 commands travel with it, and installing the plugin installs all of them — 100 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 23 lines scan A cca4bb609523
narsil is a plugin published in the GitHub repository postrv/narsil-mcp (185 stars, last pushed 11d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
trace-mcp
Framework-aware code intelligence MCP server. 88 framework integrations, 81 languages, semantic search with Signal Fusion (BM25 + PageRank + embeddings + identity), refactoring tools (rename/move/extract/codemod), change-impact analysis, security scanning, and decision/session memory.
synapse-mcp
A persistent code-knowledge graph for AI agents. Runs locally. Writes safely.
chrome-devtools-mcp
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer.
chrome-devtools-mcp
MCP configuration declaring 1 server: chrome-devtools.
bitrise
MCP configuration declaring 1 server: bitrise.
oneskills
OneScience / OneSkills skills for AI-native scientific research workflows, coding, runtime submission, debugging, and environment setup.