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 commands/ncssm-robotics/ftc-claude/create-skillgit clone --depth 1 https://github.com/ncssm-robotics/ftc-claudeWrote 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/ncssm-robotics/ftc-claude/create-skill)<a href="https://agentmods.dev/commands/ncssm-robotics/ftc-claude/create-skill"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/create-skill.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.00720 |
| Opus 5 | $0.00004 | $0.00360 |
| Sonnet 5 | $0.00002 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
create-skill 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 4d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Skill Command
Creates a new FTC skill plugin with proper structure and templates.
Usage
/create-skill <skill-name> [category]
Arguments:
skill-name: Name for the new skill (kebab-case, e.g.,rev-hub,roadrunner)category: Optional - one of:hardware,library,framework,tools,game
Examples
/create-skill rev-hub hardware
/create-skill roadrunner library
/create-skill meepmeep tools
Process
When this command is invoked:
-
Validate the skill name
- Must be kebab-case (lowercase, hyphens)
- Must not already exist in
plugins/ - Must be 64 characters or less
-
Create the plugin structure
plugins/<skill-name>/ ├── plugin.json ├── CHANGELOG.md └── skills/ └── <skill-name>/ └── SKILL.md -
Generate plugin.json with:
- Name from argument
- Category from argument (or ask user)
- Placeholder description
- MIT license
- Standard compatibility list
-
Generate SKILL.md with:
- Proper frontmatter (name, description placeholder, license, compatibility, metadata)
- Template sections (Quick Start, Key Concepts, Patterns, Anti-Patterns, Examples)
- Placeholder content marked with
[TODO: ...]
-
Generate CHANGELOG.md with:
- Initial version 1.0.0 entry
- Today's date
- "Initial release" placeholder
-
Add to marketplace.json
- Add entry to the plugins array
- Include version field set to "1.0.0"
- Set source to
./plugins/<skill-name>
-
Add to README.md skill table
- Add row to appropriate category table (FTC Skills or Contributor Tools)
- Include skill name, category, and brief description
- Ensure table stays alphabetically sorted within category
-
Prompt user to fill in:
- Description (WHAT + WHEN)
- Quick Start content
- Code examples
- Reference documentation
After Creation
Guide the user through:
- Writing a good description with FTC-specific keywords
- Adding Quick Start with working code examples
- Creating Good/Bad example comparisons
- Testing the skill activates correctly
- Verifying README.md skill table entry is accurate
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.
- 4d ago First seen · 106 lines · 8 tokens per session scan A 81cb28d9050b
create-skill is a command published in the GitHub repository ncssm-robotics/ftc-claude (4 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 720 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.