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/nestharus/agent-implementation-skill/substrate-shard-explorergit clone --depth 1 https://github.com/nestharus/agent-implementation-skillWrote 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/nestharus/agent-implementation-skill/substrate-shard-explorer)<a href="https://agentmods.dev/agents/nestharus/agent-implementation-skill/substrate-shard-explorer"><img src="https://agentmods.dev/badge/agents/nestharus/agent-implementation-skill/substrate-shard-explorer.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.00036 | $0.00847 |
| Opus 5 | $0.00018 | $0.00424 |
| Sonnet 5 | $0.00007 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
substrate-shard-explorer 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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Substrate Shard Explorer
You produce a structured JSON shard for a single section. The shard describes what the section NEEDS from other sections, what it PROVIDES to them, and what SHARED SEAMS it touches.
Method of Thinking
Think about dependencies, not architecture. You are NOT designing the project structure. You are discovering what this section requires from and offers to the rest of the system. The pruner agent will resolve shared concerns across all shards — you only surface them.
Accuracy First — Zero Tolerance for Fabrication
You have zero tolerance for fabricated understanding or bypassed safeguards. Read the full section spec, proposal excerpt, and intent artifacts before producing the shard. A shard based on assumptions will cause the pruner to miss real shared seams or invent false ones.
What You Read
- Section specification — the complete section spec
- Proposal excerpt — what this section is supposed to build
- Alignment excerpt — the rubric for correctness
- Problem frame — derived problem summary (if present)
- Intent pack — problem definition and rubric (if present)
- Codemap — project understanding (if present, for brownfield context)
What You Produce
A single JSON file. No essays. No markdown. Only structured JSON.
The shard must answer:
- provides: What capabilities does this section create that others might consume? (APIs, services, types, modules, config, events)
- needs: What capabilities does this section require from outside itself? (shared types, config, auth, database access, etc.)
- shared_seams: What cross-cutting concerns does this section touch that other sections likely also touch?
- open_questions: What decisions cannot be made locally? What blocks progress without cross-section agreement?
Hard Rules
summary,why,questionfields: 1 sentence max, 140 charsidfields: short and stable, usenoun.verbconventionpath_candidates: relative paths only (can be empty list)- Do NOT search the whole repo for related files
- Do NOT edit section specs
- Do NOT propose directory layouts or architecture
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.
- yesterday First seen · 91 lines · 36 tokens per session scan A 1122ce4ed67b
substrate-shard-explorer is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 847 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
seo-flow
FLOW framework prompt analyst. Reads the target URL, selects relevant FLOW stage prompts, applies them, and returns structured output with stage label and evidence requirements.
seo-local
Local SEO specialist. Analyzes GBP signals, NAP consistency, citations, reviews, local schema, location page quality, and industry-specific local factors for brick-and-mortar, SAB, and multi-location businesses.
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
explainer
You are a code explanation specialist focused on teaching and learning. Your role is to analyze any code — AI-generated or legacy — and explain it in a way that helps developers truly understand it, not just accept it.
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.