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/nexus-substrate/nexus-agents/readmegit clone --depth 1 https://github.com/nexus-substrate/nexus-agentsWrote 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/nexus-substrate/nexus-agents/readme)<a href="https://agentmods.dev/agents/nexus-substrate/nexus-agents/readme"><img src="https://agentmods.dev/badge/agents/nexus-substrate/nexus-agents/readme.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.00000 | $0.00710 |
| Opus 5 | $0.00000 | $0.00355 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
README 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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent persona prompts
Human-facing review personas for the Agent tool's subagent_type parameter (Claude Code) or any equivalent subagent invocation surface. These are not the same as the voter-pipeline experts in agents/ at the repo root.
When to use these vs the voter-pipeline experts
| Surface | Lives in | Output shape | Consumed by |
|---|---|---|---|
| Voter-pipeline experts | agents/*.md (repo root) |
Structured JSON with confidence, severity, issues[], suggestions[], etc. |
ConsensusEngine, voterPanel, consensus_vote MCP tool |
| Persona prompts (this dir) | .claude/agents/*.md |
Human-readable narrative review with categorized findings | Direct human review, ad-hoc subagent dispatch via the Agent tool |
The two surfaces coexist. Architect QA on epic #2385 explicitly authorized this split: "adopt only as subagent prompt templates, not as new voter roles, to avoid panel inflation." Don't merge them.
Personas
| File | Purpose | Voter-pipeline counterpart |
|---|---|---|
code-reviewer.md |
Senior code-review persona (Staff Engineer voice). Five-axis assessment: correctness, readability, architecture, security, performance. Findings categorized Critical / Important / Suggestion. | agents/code-expert.md |
security-auditor.md |
Security audit persona. Vulnerability scan, threat modeling, OWASP-aligned findings, severity classification. | agents/security-expert.md |
test-engineer.md |
Test-engineer persona. Coverage assessment, missing edge cases, test-quality review (DAMP, AAA, naming). | agents/testing-expert.md |
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.
- 4d ago First seen · 53 lines · 0 tokens per session scan A 60ade45b3b4e
README is an agent published in the GitHub repository nexus-substrate/nexus-agents (18 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 710 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.