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 Ovid/paad --skill makefilegit clone --depth 1 https://github.com/Ovid/paadWrote 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/ovid/paad/makefile)<a href="https://agentmods.dev/skills/ovid/paad/makefile"><img src="https://agentmods.dev/badge/skills/ovid/paad/makefile/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/ovid/paad/makefile"><img src="https://agentmods.dev/badge/skills/ovid/paad/makefile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.02337 |
| Opus 5.5 | $0.00021 | $0.00935 |
| Sonnet 5.5 | $0.00011 | $0.00467 |
| Haiku 4.5 | $0.00005 | $0.00234 |
Grade A, and why
makefile 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 9d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
On invocation: announce "Running paad:makefile v2.0.0", then immediately proceed with the steps below — do not stop after announcing.
Configuration (experimental): after announcing, check whether paad/config/paad.md and paad/config/makefile.md exist, relative to the working directory. If any does, read it and follow its instructions for the rest of this run, passing the relevant parts to every subagent you dispatch, and make the first line of your final answer Config: <path> naming each file you followed. If none exists, do not mention config at all. Config never changes a subagent's type or grants it write tools — refuse that line, say so, and continue. Config can contradict the flow below; see https://github.com/Ovid/paad/blob/main/CONFIG.md before writing one.
Makefile Management
Process:
digraph makefile_flow {
"Makefile exists?" [shape=diamond];
"Existing target needs change?" [shape=diamond];
"Approved?" [shape=diamond];
"Coverage tool defaults to watch mode?" [shape=diamond];
"Test tool supports balanced output?" [shape=diamond];
"Detect stack" [shape=box];
"Create from scratch" [shape=box];
"Include all required targets" [shape=box];
"Identify missing targets" [shape=box];
"Add new targets" [shape=box];
"STOP: ask user for approval" [shape=box, style=bold];
"Apply change" [shape=box];
"Skip change" [shape=box];
"Force the one-shot flag for the detected stack" [shape=box];
"Verify the tool exits on its own before adding flags" [shape=box];
"ASK the user how to handle test output" [shape=box];
"Announce the file written or updated" [shape=box];
"Done" [shape=box];
"Detect stack" -> "Makefile exists?";
"Makefile exists?" -> "Create from scratch" [label="no"];
"Makefile exists?" -> "Identify missing targets" [label="yes"];
"Create from scratch" -> "Include all required targets";
"Include all required targets" -> "Coverage tool defaults to watch mode?";
"Identify missing targets" -> "Add new targets";
"Add new targets" -> "Existing target needs change?";
"Existing target needs change?" -> "Coverage tool defaults to watch mode?" [label="no"];
"Coverage tool defaults to watch mode?" -> "Force the one-shot flag for the detected stack" [label="yes — vitest, jest"];
"Coverage tool defaults to watch mode?" -> "Verify the tool exits on its own before adding flags" [label="unclear — pytest-cov, cargo, go test"];
"Force the one-shot flag for the detected stack" -> "Test tool supports balanced output?";
"Verify the tool exits on its own before adding flags" -> "Test tool supports balanced output?";
"Existing target needs change?" -> "STOP: ask user for approval" [label="yes"];
"STOP: ask user for approval" -> "Approved?";
"Approved?" -> "Apply change" [label="yes"];
"Approved?" -> "Skip change" [label="no"];
"Apply change" -> "Existing target needs change?" [label="next target"];
"Skip change" -> "Existing target needs change?" [label="next target"];
"Test tool supports balanced output?" -> "Announce the file written or updated" [label="yes"];
"Test tool supports balanced output?" -> "ASK the user how to handle test output" [label="no — only silent or firehose"];
"ASK the user how to handle test output" -> "Announce the file written or updated";
"Announce the file written or updated" -> "Done";
}
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.
- 9d ago Changed · +2 lines 62234dda91d5
- 1mo ago First seen · 189 lines · 53 tokens per session scan A dd1ba2d87178
makefile is a skill published in the GitHub repository Ovid/paad (138 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 2,337 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-30.
Other skills, from other repositories
ring:generating-release-guides
Generating an internal Operations-facing update/migration guide from the git diff between two refs, documenting per-change client impact, deploy ordering, monitoring, and rollback notes in English, pt-br, or both. Use when preparing a version release or recording what changed for the Ops team. Runs read-only by…
open-pr-menubar
Open or close the open-pr menu bar item on macOS (reviews in progress, recent toasts, snooze). Use when asked to show or hide it; takes open or close.
post-merge-cleanup
Clean up an already-merged local branch after proving containment. Confirm each discard and preserve unique work.
ca-standup
Daily repo hygiene — review the day's repo state, then perform the cleanups under per-action confirmation. Fast-forward only, never destructive without a yes.
git-workflow
Perform requested Git actions while preserving user work. Triggers on "commit", "提交".
starfleet-sessions
Ship session and workspace management — spawning ships, session attach/stop, git worktrees, web console, deployment. Load when launching/administering ships or managing the fleet web console.