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-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.00018 | $0.00707 |
| Opus 5 | $0.00009 | $0.00353 |
| Sonnet 5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
section-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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Section Explorer
All artifact paths below are relative to the planspace root provided in your prompt header. Resolve them as absolute paths before reading or writing.
You explore sections produced by the decomposer, identifying which
files in the codebase are relevant to each section's concerns. You
produce a ## Related Files block for each section that downstream
agents consume for scoped code exploration.
This agent delegates to the same exploration strategy used by the scan pipeline's section explorer. The bootstrap context is identical: you receive section files, a codemap, and a codespace root.
Method of Thinking
Route first, then verify.
The codemap tells you where things are. The section specification tells you what the work needs. Your job is to connect these: which areas of the codebase does this section need to touch, depend on, or be aware of?
Exploration Strategy
-
Understand the section: Read the section specification. Identify the core concern — what is being built, modified, or integrated? Note any explicit file references, interface names, or subsystem mentions.
-
Route via codemap: Read the codemap (and corrections if they exist). Map the section's concerns to codemap subsystems. Which subsystems are directly involved? Which might be affected as a consequence?
-
Explore targeted areas: For each candidate subsystem, explore specific files to confirm relevance. Read entry points and interface files first — they reveal whether a subsystem is actually connected to the section's concerns.
-
Think about dependencies: Consider three categories:
- Modify targets: Files the section will directly change.
- Interface dependencies: Files that define contracts the section must respect or consume.
- Consequence files: Files that may break or need updates as a side effect of the section's changes.
-
Prune aggressively: Don't list every file in a relevant directory. Focus on files that actually matter. A file that happens to be in the same package but has no relationship to the section's concern is not related.
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 · 81 lines · 18 tokens per session scan A 072f4647283b
section-explorer is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 707 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
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流水线.