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 skills/thettwe/nyann/fleetnpx skills add thettwe/nyann --skill fleetgit clone --depth 1 https://github.com/thettwe/nyannWrote 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/thettwe/nyann/fleet)<a href="https://agentmods.dev/skills/thettwe/nyann/fleet"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/fleet.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.00208 | $0.01471 |
| Opus 5 | $0.00104 | $0.00736 |
| Sonnet 5 | $0.00042 | $0.00294 |
| Haiku 4.5 | $0.00021 | $0.00147 |
Grade A, and why
fleet 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 3d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fleet
Plugin root:
<plugin_root>/skills/fleet/SKILL.md— scripts live at<plugin_root>/bin/fleet.sh(registry CRUD) and<plugin_root>/bin/fleet-doctor.sh(bulk audit + dashboard).
Read-only across the board: the registry file is the only thing this skill
ever writes, and every registry mutation previews first. The registry lives
at ~/.claude/nyann/fleet.json and holds LOCAL working-copy paths — it is
deliberately distinct from the sentinel watch-list (GitHub slugs for remote
CI polling); an entry's optional repo slug is the join key between the two.
1. Registry management
All CRUD goes through bin/fleet.sh (--fleet-file only in tests):
| User intent | Invocation |
|---|---|
| "add this repo" | bin/fleet.sh --add <path> [--name n] [--repo o/r] [--profile p] [--tag t] |
| "add and watch its PRs too" | append --watch (mirrors the slug into the sentinel watch-list; resolves the slug from the origin remote when --repo is omitted) |
| "remove X" | bin/fleet.sh --remove <name-or-path> |
| "list my fleet" | bin/fleet.sh --list (JSON — render it as a table) |
| "scan ~/Works for repos" | bin/fleet.sh --scan <dir> [--depth n] |
| "clean out dead entries" | bin/fleet.sh --prune |
| "what org repos am I missing?" | bin/fleet.sh --suggest-org <org> (gh best-effort, advisory only — nyann never clones) |
--scan and --prune are preview-first: the bare call prints the
candidate list and writes NOTHING. Show the list, confirm with
AskUserQuestion, then re-run with --apply. Never jump straight to
--apply.
Add validation to expect: the path must be a git repo (it is canonicalised
to the toplevel, so re-adding a subdir dedupes); a name colliding with a
different repo's name is refused — pass a distinct --name.
2. The health dashboard
bin/fleet-doctor.sh [--json | --markdown] [--cached] [--drift | --explain]
[--tag t] [--only a,b] [--jobs n] [--timeout s]
[--persist] [--stale-days n] [--threshold n]
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.
- 3d ago First seen · 112 lines · 208 tokens per session scan A 14a15c2f68bd
fleet is a skill published in the GitHub repository thettwe/nyann (6 stars, last pushed 4d ago), licensed MIT. It adds 208 tokens to every session and 1,471 once invoked, about $0.0010 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 skills, from other repositories
code-gauntlet
Prefer this skill for code review requests — it runs a multi-agent pipeline with blind challenge verification for high-confidence results. Trigger for ANY of these situations: (1) user says "review" in the context of code, PRs, MRs, branches, diffs, or changes, (2) user references a PR/MR number and wants feedback or…
publish-github-release
Use this whenever the user asks to ship, publish, release, tag, or cut a new version of the project — OR when CHANGELOG.md has an "Unreleased" / in-progress section ready to be shipped. The skill bumps the version across all version-bearing files, regenerates the CHANGELOG entry from git log since the last tag…
open-pr
Use this skill to submit the commits on the current branch as one pull request against a GitHub repository. Push the branch, open the PR with an imperative title and a body that names what changed and why, and post a follow-up ping only when CODEOWNERS resolves to one person. One branch per run, one pull request per…
github-design
Use when setting up GitHub repositories, workflows, issue templates, or project organization - enforces best practices for .github folder structure, reusable workflows, branch protection, CODEOWNERS, labels, and GitHub Projects. Triggers on: GitHub, repository setup, workflow, Actions, issue template, PR template…
oss-search
This skill should be used when searching for open source issues, vetting contributions, interpreting viability scores, or planning a search strategy. Covers multi-strategy search, vetting workflow, and score interpretation.
mcp-discovery
Dynamic MCP package discovery at runtime. Instead of relying on a static registry, this skill verifies MCP availability by querying npm, GitHub, and vendor documentation.