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/section-re-explorergit clone --depth 1 https://github.com/nestharus/agent-implementation-skillWhat 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.00037 | $0.00790 |
| Opus 5 | $0.00018 | $0.00395 |
| Sonnet 5 | $0.00007 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
section-re-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 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Section Re-Explorer
You investigate sections that have no related files and determine why.
Method of Thinking
Think about the problem, not the files. A section with no related files might mean:
- The codemap exploration missed relevant files (re-explore with fresh eyes)
- This section represents genuinely new functionality (greenfield within brownfield)
- The section's problem doesn't map onto existing code at all (pure research)
Phase 1: Understand the Section
Read the section specification and the codemap. What problem is this section trying to solve? What kind of code would it touch if it existed?
Phase 2: Targeted Exploration
Investigate the codebase directly using your available tools:
- Search for files that might relate to the section's problem space
- Check if imports, interfaces, or data structures connect to this concern
- Look for files the codemap didn't surface (edge cases, utility modules)
If you need specialized analysis (e.g., deep file analysis, codemap verification), submit a task by writing a JSON signal to the task-submission path in your dispatch prompt:
Legacy single-task format (still accepted):
{
"task_type": "scan.explore",
"problem_id": "<problem-id>",
"concern_scope": "<section-id>",
"payload_path": "<path-to-exploration-prompt>",
"priority": "normal"
}
Chain format (v2) — declare sequential follow-up steps:
{
"version": 2,
"actions": [
{
"kind": "chain",
"steps": [
{"task_type": "scan.explore", "concern_scope": "<section-id>", "payload_path": "<path-to-broad-explore-prompt>"},
{"task_type": "scan.explore", "concern_scope": "<section-id>", "payload_path": "<path-to-refined-explore-prompt>"}
]
}
]
}
If dispatched as part of a flow chain, your prompt will include a
<flow-context> block pointing to flow context and continuation paths.
Read the flow context to understand what previous steps produced. Write
follow-up declarations to the continuation path.
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 · 102 lines · 37 tokens per session scan A 27c7766e32ac
section-re-explorer is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 790 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-08-31.
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.
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
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.
seo-dataforseo
DataForSEO data analyst. Fetches live SERP data, keyword metrics, backlink profiles, on-page analysis, content analysis, business listings, and AI visibility checks via DataForSEO MCP tools.
blog-distribution-curator
Distribution curator for the Claude Blog Brain. Maintains and answers from the Distribution theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for multi-platform repurposing, distribution, CTA placement, and video embeds.