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.
git clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/commands/davistroy/claude-marketplace/new-skill.eval)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/new-skill.eval"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/new-skill.eval/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/commands/davistroy/claude-marketplace/new-skill.eval"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/new-skill.eval.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00597 |
| Opus 5 | $0.00000 | $0.00298 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
new-skill.eval 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 10d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval: /new-skill
Purpose
Generates a new skill file with proper nested directory structure and required frontmatter. Good output: a skills/<name>/SKILL.md file with name and description in frontmatter, proactive trigger conditions, and the correct nested structure.
Fixtures
None — generates files in the plugin directory.
Test Scenarios
S1: Happy path — generate a new skill
Invocation: /new-skill (then provide name and description when prompted)
Interaction:
- Name:
diff-summary - Description:
Summarize staged git changes before committing
Must:
- Creates
plugins/personal-plugin/skills/diff-summary/SKILL.md - SKILL.md has
name: diff-summaryin frontmatter - SKILL.md has
description:in frontmatter - File is named exactly
SKILL.md(uppercase) - Directory name matches the
namefield exactly
Should:
- Includes "Proactive Triggers" section describing when Claude should suggest the skill
- Includes
allowed-toolsfrontmatter field - Includes at least one usage example
Must NOT:
- Create
skills/diff-summary.md(flat structure — skill would not be discovered) - Create
skills/diff-summary/skill.md(wrong case — skill would not be discovered) - Omit
namefrom frontmatter (skill would not be registered)
S2: Skill name provided as argument
Invocation: /new-skill audit-log
Must:
- Creates
plugins/personal-plugin/skills/audit-log/SKILL.md -
name: audit-login frontmatter
S3: Error — skill already exists
Invocation: /new-skill ship
Must:
- Detects
skills/ship/SKILL.mdalready exists - Prompts to confirm overwrite or aborts
- Does not silently overwrite the existing
shipskill
S4: Validate created skill
After running S1, run:
Invocation: /validate-plugin personal-plugin
Must:
- The new
diff-summaryskill passes validation - No missing
nameordescriptionerrors reported
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.
- 10d ago First seen · 86 lines · 0 tokens per session scan A 9c2394cf0675
new-skill.eval is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 597 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.