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 agents/intercooperative-network/icn/icn-docs-specgit clone --depth 1 https://github.com/InterCooperative-Network/icnWrote 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/agents/intercooperative-network/icn/icn-docs-spec)<a href="https://agentmods.dev/agents/intercooperative-network/icn/icn-docs-spec"><img src="https://agentmods.dev/badge/agents/intercooperative-network/icn/icn-docs-spec.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.00029 | $0.00675 |
| Opus 5 | $0.00015 | $0.00338 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
icn-docs-spec 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 3d 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
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago First seen · 99 lines · 29 tokens per session scan A 5994902ae827
icn-docs-spec is an agent published in the GitHub repository InterCooperative-Network/icn (10 stars, last pushed today), licensed AGPL-3.0. It adds 29 tokens to every session and 675 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-31.
Other agents, from other repositories
literature-scout
经济金融学术文献侦察子智能体。负责系统性检索、筛选和分析学术文献，构建引文网络，识别研究缺口。与 generator-reviewer 分离原则：scout 只负责侦察，不参与评分和写作。.
mira
CEO of Thinking Machines Lab — the engineer-diplomat. Measured, allergic to both hype and doom, insists on contact with reality.
golang-code-writer
Always use this agent when you need to write, generate, or create new Go code, including functions, structs, interfaces, methods, or complete packages. Examples: Context: User needs help implementing a new feature in their Go application. user: 'I need to write a function that validates email addresses using regex'…
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
pm-orchestrator
Use this agent to plan, sequence, and orchestrate the whole AI team across the SDD lifecycle. It owns planning-first governance (roadmap → plan → approval → execution), GitHub issue/label governance, and delegation to the eight specialist agents. It drives the document lifecycle through the plugin's native SDD skills…
api-reviewer
Read-only reviewer focused on API consistency, migration safety, and boundary-validation gaps — flags problems precisely, never edits code itself.