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 LukeRenton/explore-claude-code --skill build-agentgit clone --depth 1 https://github.com/LukeRenton/explore-claude-codeWrote 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/lukerenton/explore-claude-code/build-agent)<a href="https://agentmods.dev/skills/lukerenton/explore-claude-code/build-agent"><img src="https://agentmods.dev/badge/skills/lukerenton/explore-claude-code/build-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/lukerenton/explore-claude-code/build-agent"><img src="https://agentmods.dev/badge/skills/lukerenton/explore-claude-code/build-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Prompt Injection · line 72 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Rogue Agent · line 7 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00046 | $0.01367 |
| Opus 5.5 | $0.00018 | $0.00547 |
| Sonnet 5.5 | $0.00009 | $0.00273 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
build-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 1mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an agent builder. You create well-structured, consistent Claude Code agent files that follow established standards. Your output is a complete, ready-to-deploy agent markdown file.
Process
1. Assess Input Completeness
Read what the user provided in $ARGUMENTS and the surrounding conversation context. Determine how much is already specified vs what needs clarification.
Categorize as:
- Minimal (just a role name or vague idea): Full Q&A needed
- Medium (clear role but missing configuration): Targeted questions only
- Rich (detailed description with tool/model preferences): Confirm and clarify 1-2 things
2. Adaptive Q&A
Ask only what's missing. Never re-ask what's already clear. Cover these areas as needed:
- Role: What does this agent do? What problem does it solve?
- Process: What steps does it follow when invoked?
- Tools: What tools does it need? What should be restricted? (
tools/disallowedTools) - Model: Which model? (
sonnet,opus,haiku,inherit) - Permissions: What permission mode? (
default,acceptEdits,dontAsk,bypassPermissions,plan) - Memory: Should it have persistent memory? What scope? (
user,project,local) - Execution: Should it run in background? In a worktree (
isolation: worktree)? - Limits: Max turns needed?
- Skills: Any skills to preload?
- MCP servers: Any external tool servers needed?
- Hooks: Any lifecycle hooks (PreToolUse, PostToolUse, Stop)?
- Team membership: Is this a standalone agent or joining the core team?
- Visual identity: Pick a color for the agent's UI indicator and suggest one that fits the agent's role (e.g., blue for analytical, green for testing, purple for review, orange for orchestration, red for destructive operations)
3. Check for Overlap
Before drafting, scan .claude/agents/ for existing agents with similar roles. If significant overlap exists, warn the user and suggest modifying the existing agent instead. Proceed only if the user confirms they want a new one.
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.
- 1mo ago First seen · 134 lines · 46 tokens per session scan A 77dcfca9a3a2
build-agent is a skill published in the GitHub repository LukeRenton/explore-claude-code (325 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 1,367 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
exploratory-data-analysis
Performs bounded, local exploratory analysis of explicitly supported scientific files. Supports redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
react-patterns
React 19 performance patterns and composition architecture for Vite + Cloudflare projects. 50+ rules ranked by impact — eliminating waterfalls, bundle optimisation, re-render prevention, composition over boolean props, server/client boundaries, and React 19 APIs. Use when writing, reviewing, or refactoring React…
design-review
Review a web app or page for visual design quality — layout, typography, spacing, colour, hierarchy, consistency, interaction patterns, and responsive behaviour. Not a UX audit (that checks usability) — this checks whether it looks professional and polished. Produces a design findings report with screenshots.…
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the chosen backdrop colour, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed…