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 saadshahd/moo.md --skill flygit clone --depth 1 https://github.com/saadshahd/moo.mdWrote 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/saadshahd/moo.md/fly)<a href="https://agentmods.dev/skills/saadshahd/moo.md/fly"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/fly/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/saadshahd/moo.md/fly"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/fly.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.00040 | $0.00669 |
| Opus 5 | $0.00020 | $0.00334 |
| Sonnet 5 | $0.00008 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
fly 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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the pilot of one thought. Several agents fly its parts at once; you never fly a part. Speak in the thought's own words, and ask the user nothing before takeoff.
Words
- destination — what will be true when it lands, what it must not touch, and every detail the thought named. In the user's words.
- part — the piece of the destination one agent carries and may change alone. Two agents never share a part.
- log — what the medium already keeps of what happened. Never a file made for the flight.
Medium
The flight uses what is already there. Find each of these in the project and the harness before anything else; add nothing for the flight's sake.
| Needed | Use what exists |
|---|---|
| Agents flying their parts at once | Solo spawn_agent, the Agent tool, claude -p in a terminal, one worktree per part |
| The log: where every agent reads the destination and where what happened shows | git across worktrees, the Solo scratchpad, the agents' own returns, the tracker or PR the project already uses |
| Where the user looks | the running app, a browser they can drive |
One of the three is missing → say which and stop.
Takeoff
-
Read the thought back as the destination, in the log, where the user can see it. Do not wait for a yes: a correction from the user changes it for every agent.
-
Cut the destination into parts. An agent not worth its own warm-up is not a part. One part → say so and stop.
-
Brief each agent in plain words:
You fly `<part>` of the destination in <log>. Read the destination before you start and before every change you commit. Stop, say why in <log>, and wait, when any holds: - your part needs another's part - your part needs the destination changed - you need a fact you cannot get When you believe your part is done: stop and state what you did against your part. You do not land the flight. -
Start every agent. A start that fails stays in the log as a part not flown.
-
Bring up where the user looks. Say what they will see first, and roughly when.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 58 lines · 40 tokens per session scan A ea7eca269f3a
fly is a skill published in the GitHub repository saadshahd/moo.md (34 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 669 once invoked, about $0.0002 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-09-07.
Other skills, from other repositories
lark-task
A Feishu task skill for managing to-do items, task lists, subtasks, assignments, attachments, and task-focused agents.
lark-calendar
A tool for managing Feishu calendars, meetings, attendees, and meeting rooms. Feishu is a workplace collaboration platform used for schedules and team coordination.
lark-okr
A Feishu OKR skill for managing objectives and key results: goals paired with measurable outcomes used to track progress.
lark-approval
A tool for managing approval requests in Feishu, such as requests waiting for a decision or already completed. It handles actions and searches related to approval records rather than ordinary tasks.
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
manage-tickets
Create, edit, search, transition, close, and triage Jira tickets via the Atlassian MCP. Use when asked to file a bug, request a feature, create a task, log a defect, search the backlog, triage findings into the tracker, edit ticket fields, transition status, or manage Jira work items. Also use when the user says…