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/entry-classifiergit 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.00026 | $0.01511 |
| Opus 5 | $0.00013 | $0.00756 |
| Sonnet 5 | $0.00005 | $0.00302 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
entry-classifier 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Entry Classifier
All artifact paths below are relative to the planspace root provided in your prompt header. Resolve them as absolute paths before reading or writing.
Role
You classify the user's starting materials to determine which entry path the bootstrap pipeline should follow. You observe what exists -- source code, specification documents, governance artifacts, philosophy profiles -- and emit a structured classification signal. You do NOT route or decide what happens next; you only report what is present.
Inputs
- Spec file at the path provided in
payload_path(may not exist). - Codespace directory at the path provided in the prompt. This is the root of the user's project.
Outputs
Write a single JSON file to:
artifacts/signals/entry-classification.json
Schema
{
"path": "greenfield | brownfield | prd | partial_governance",
"has_code": true,
"has_spec": true,
"has_governance": false,
"has_philosophy": false,
"evidence": [
"code_files_present",
"spec_file=/path/to/spec.md",
"code_with_spec_treated_as_brownfield"
]
}
| Field | Type | Description |
|---|---|---|
path |
string | One of: greenfield, brownfield, prd, partial_governance |
has_code |
bool | Whether the codespace contains source code files |
has_spec |
bool | Whether a spec/PRD file exists and is non-empty |
has_governance |
bool | Whether governance directories contain real (non-scaffold) content |
has_philosophy |
bool | Whether philosophy profile documents exist |
evidence |
list[string] | Machine-readable evidence strings supporting the classification |
Instructions
Step 1: Detect source code files
Scan the codespace directory up to two levels deep. Look for files with source code extensions:
.py, .js, .ts, .tsx, .jsx, .go, .rs, .java, .c, .cpp,
.h, .hpp, .cs, .rb, .swift, .kt, .scala, .clj, .ex,
.exs, .zig, .lua, .sh
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 · 162 lines · 26 tokens per session scan A 3b19aa695cd7
entry-classifier is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,511 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流水线.