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 ncssm-robotics/ftc-claude --skill code-reviewgit 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/skills/ncssm-robotics/ftc-claude/code-review)<a href="https://agentmods.dev/skills/ncssm-robotics/ftc-claude/code-review"><img src="https://agentmods.dev/badge/skills/ncssm-robotics/ftc-claude/code-review/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/ncssm-robotics/ftc-claude/code-review"><img src="https://agentmods.dev/badge/skills/ncssm-robotics/ftc-claude/code-review.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.00047 | $0.01080 |
| Opus 5.5 | $0.00019 | $0.00432 |
| Sonnet 5.5 | $0.00009 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
code-review 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 2mo 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FTC Code Review Checks
This skill defines the code quality and structure checks for FTC marketplace skills. These checks are the source of truth for both local reviews (/review) and PR bot reviews.
Structure Checks (Errors)
These checks must pass - errors block PR merge.
Plugin Directory Structure
-
plugins/<skill-name>/directory exists -
plugins/<skill-name>/plugin.jsonexists -
plugins/<skill-name>/CHANGELOG.mdexists -
plugins/<skill-name>/skills/<skill-name>/directory exists -
plugins/<skill-name>/skills/<skill-name>/SKILL.mdexists
plugin.json Validation
- File is valid JSON (no syntax errors)
- Has
namefield matching directory name - Has
versionfield in semver format (X.Y.Z) - Has
descriptionfield (non-empty string) - Has
authorfield as object (NOT a string) - Author object has
nameproperty - Has
keywordsarray (NOTtags) - Keywords array includes "ftc"
SKILL.md Frontmatter Validation
- File starts with
---(YAML frontmatter) - Has
namefield matching directory name - Has
descriptionfield (non-empty, < 1024 chars) - Has
licensefield - Has
metadataobject - Has
metadata.versionfield matching plugin.json version - Has
metadata.categoryfield
Version Consistency
- Version in
plugin.jsonmatches version in SKILL.md frontmatter - Version in
marketplace.jsonentry matches plugin.json (if listed)
Content Quality Checks (Warnings)
These are recommendations - warnings don't block merge but should be addressed.
Description Quality
- Description explains WHAT the skill does
- Description explains WHEN to use it (trigger words)
- Description contains FTC-specific keywords
- Description is under 1024 characters
SKILL.md Content
- File is under 500 lines (use progressive disclosure)
- Has "Quick Start" or "Getting Started" section
- Has code examples (
java orkotlin blocks) - Has "Anti-Pattern" or "Don't" section with bad examples
- No
[TODO: ...]placeholder markers remaining
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.
- 2mo ago First seen · 124 lines · 47 tokens per session scan A 9dcfdc2a74e5
code-review is a skill published in the GitHub repository ncssm-robotics/ftc-claude (5 stars, last pushed 9mo ago), licensed MIT. It adds 47 tokens to every session and 1,080 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-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…