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/update-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/update-skill)<a href="https://agentmods.dev/commands/ncssm-robotics/ftc-claude/update-skill"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/update-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.1 | $0.00010 | $0.00921 |
| Opus 5 | $0.00005 | $0.00461 |
| Sonnet 5 | $0.00002 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
update-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 6d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Skill Command
Analyzes git changes and generates properly formatted changelog entries for a skill.
Important: This command only creates changelog entries. Version bumping is handled automatically by the release process when the PR is merged.
Usage
/update-skill <skill-name>
Arguments:
skill-name: Name of the skill to update (must exist inplugins/)
Examples
/update-skill pinpoint
/update-skill pedro-pathing
/update-skill decode
Process
When this command is invoked:
-
Validate the skill exists
- Check
plugins/<skill-name>/directory exists - Check
CHANGELOG.mdexists in the plugin directory - Check
## [Unreleased]section exists in CHANGELOG.md
- Check
-
Analyze git changes
- Run
git status plugins/<skill-name>/to see modified files - Run
git diff plugins/<skill-name>/to see specific changes - Identify new files, modified files, and deleted files
- Run
-
Categorize changes into changelog categories:
- Added - New files, new features, new sections
- Changed - Modified behavior, updated documentation
- Fixed - Bug fixes, corrections
- Removed - Deleted features, removed sections
- Deprecated - Features marked for removal
- Security - Security-related fixes
-
Generate proposed entries
- Create concise, descriptive entries for each change
- Use imperative mood ("Add X" not "Added X")
- Group related changes together
-
Present to user for confirmation
- Show proposed entries
- Allow user to edit, add, or remove entries
- Confirm before writing
-
Update CHANGELOG.md
- Append entries to
## [Unreleased]section - Preserve existing unreleased entries
- Maintain proper formatting
- Append entries to
Output Example
Analyzing changes for skill: pinpoint
Git status shows:
modified: skills/pinpoint/SKILL.md (47 lines changed)
new file: skills/pinpoint/scripts/calibrate.py
Proposed changelog entries:
### Added
- Calibration script for automated pod offset calculation
### Changed
- Updated Quick Start section with calibration workflow
- Added troubleshooting section for IMU drift issues
Confirm these entries? [Y/n/edit]
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.
- 6d ago First seen · 140 lines · 10 tokens per session scan A 55e4230abb6f
update-skill is a command published in the GitHub repository ncssm-robotics/ftc-claude (4 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 921 once invoked, about $0.0001 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.