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 skills add Benknightdark/neo-skills --skill neo-sub-agentgit clone --depth 1 https://github.com/Benknightdark/neo-skillsWrote 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/skills/benknightdark/neo-skills/neo-sub-agent)<a href="https://agentmods.dev/skills/benknightdark/neo-skills/neo-sub-agent"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-sub-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/benknightdark/neo-skills/neo-sub-agent"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-sub-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 23 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.1 | $0.00065 | $0.01079 |
| Opus 5 | $0.00032 | $0.00540 |
| Sonnet 5 | $0.00013 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
neo-sub-agent 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 11d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neo Sub-Agent
Use this skill to design and generate focused sub-agent definitions for developer CLIs. Keep the user in control of scope, permissions, and target clients.
Core Rule
Do not invent client-specific schema. If the requested CLI, field, or file location is not documented in references/client-adapters.md or discoverable in the project, state the missing fact and generate only a neutral blueprint.
Workflow
1. Perceive
- Inspect the project before asking questions:
- Existing agent definitions:
.claude/agents/,.codex/agents/,.github/agents/,.agents/skills/. - Project guidance:
AGENTS.md,CLAUDE.md,GEMINI.md,.github/copilot-instructions.md. - Related skills or conventions in
skills/,.agents/skills/,.github/skills/,.claude/skills/,.codex/skills/.
- Existing agent definitions:
- Identify the target clients from the user request or project evidence:
claude,codex,copilot,agy, or multiple. - If multiple clients are plausible and the request does not specify one, ask one concise question before writing files.
2. Decide Whether a Sub-Agent Fits
Read references/sub-agent-design.md when the request involves architecture, multiple agents, or tradeoffs.
Use a sub-agent when at least one is true:
- The work produces verbose logs, search results, or file reads that should not pollute the main context.
- The work is a repeated specialist role such as code review, planning, test execution, research, migration analysis, or docs verification.
- The work can run independently or in a clearly bounded sequence.
- The role needs stricter tool access, sandboxing, model choice, or output contract than the main agent.
Prefer a normal skill or main-conversation instruction when:
- The task is a quick, targeted change.
- The agent needs frequent back-and-forth with the user.
- Multiple workers would edit the same files concurrently.
- The workflow depends on undocumented client behavior.
3. Define the Agent Spec
Collect or infer these fields, using safe defaults where reasonable:
name: lowercase kebab-case, under 64 characters.description: trigger-focused; state exactly when to use the agent.instructions: role, workflow, constraints, and output contract.clients: target clients.scope:projectby default; useuseronly when the user asks for reusable personal agents.tools: use the smallest useful set; prefer read-only for reviewers, researchers, planners, and auditors.modeland reasoning effort: omit unless the user asks or the client-specific reference gives a clear default.handoff: what the parent agent should pass in and what the sub-agent must return.validation: commands, checks, or review criteria the sub-agent should run or report.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/templates/antigravity-skill.md 866 B
- assets/templates/claude-agent.md 42 B
- assets/templates/codex-agent.toml 9 B
- assets/templates/copilot-agent.md 42 B
- evals/eval_queries.json 1.2 KB
- evals/evals.json 2.3 KB
- evals/files/sample-sub-agent-spec.json 783 B
- references/client-adapters.md 4.6 KB
- references/sub-agent-design.md 5.5 KB
- scripts/render-sub-agent.py 14 KB runs code
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.
- 11d ago First seen · 107 lines · 65 tokens per session scan A 565547fabf79
neo-sub-agent is a skill published in the GitHub repository Benknightdark/neo-skills (7 stars, last pushed 5d ago), licensed MIT. It adds 65 tokens to every session and 1,079 once invoked, about $0.0003 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 skills, from other repositories
html-portal-generator
Convert a codebase into a self-contained HTML portal app for ingestion into AI application systems. Produces a single deployable HTML file with embedded CSS, JS, and data.
api-designer
Design RESTful APIs with best practices for consistency and usability.
coding-assistant
Provides coding assistance with best practices and code review.
debug-helper
Systematic debugging approach for identifying and fixing issues.
git-workflow
Git best practices for version control and collaboration.
test-writer
Write thorough tests following TDD and BDD principles.