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 TonyWu20/fortran-dev-pipeline --skill compile-plangit clone --depth 1 https://github.com/TonyWu20/fortran-dev-pipelineWrote 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/tonywu20/fortran-dev-pipeline/compile-plan)<a href="https://agentmods.dev/skills/tonywu20/fortran-dev-pipeline/compile-plan"><img src="https://agentmods.dev/badge/skills/tonywu20/fortran-dev-pipeline/compile-plan/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/tonywu20/fortran-dev-pipeline/compile-plan"><img src="https://agentmods.dev/badge/skills/tonywu20/fortran-dev-pipeline/compile-plan.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.00082 | $0.01250 |
| Opus 5 | $0.00041 | $0.00625 |
| Sonnet 5 | $0.00016 | $0.00250 |
| Haiku 4.5 | $0.00008 | $0.00125 |
Grade A, and why
compile-plan 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 10d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
compile-plan
Compiles TOML plan documents with Before/After content into per-task shell
scripts that apply changes via sd -F (fixed-string replacement). The LLM
executor just runs the script instead of interpreting code changes.
Invocation
/compile-plan <path-to-plan.toml>
Plugin Root Resolution
Resolve <plugin-root> before running any command below. Run the following command once and record the printed path — use it as the literal value everywhere <plugin-root> appears:
python3 -c "
import json; from pathlib import Path
p = Path.home() / '.claude/plugins/installed_plugins.json'
data = json.loads(p.read_text())
for key in ['fortran-dev-pipeline@my-claude-marketplace', 'fortran-dev-pipeline@local']:
if key in data['plugins']:
print(data['plugins'][key][0]['installPath']); break
"
If the command prints nothing, the plugin is not registered — stop immediately and report: "Plugin root could not be resolved from installed_plugins.json." Do not guess or construct the path manually.
How It Works
- Parses the TOML plan document — each task has explicit
file,before,afterfields - Generates a Python runner per task with base64-encoded content +
sd -Fcalls - Produces a
manifest.jsonlisting all compiled tasks
The generated scripts handle:
- replace:
sd -F <before> <after> <file>(including insertions via context anchors) - create: write file content directly
- delete:
sd -F <before> '' <file> - multi-change: sequential
sdcalls within a single task script
Usage
# Compile a TOML plan (generates compiled/ directory sibling to the plan)
python3 <plugin-root>/skills/compile-plan/scripts/compile_plan.py <plan.toml>
# Dry run — parse and report without generating scripts
python3 <plugin-root>/skills/compile-plan/scripts/compile_plan.py <plan.toml> --dry-run
# Custom output directory
python3 <plugin-root>/skills/compile-plan/scripts/compile_plan.py <plan.toml> --output-dir /tmp/compiled
# Legacy markdown plans still work (with deprecation warning)
python3 <plugin-root>/skills/compile-plan/scripts/compile_plan.py <plan.md>
What ships with it
2 files 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.
- 10d ago First seen · 139 lines · 82 tokens per session scan A 052cdb8879dd
compile-plan is a skill published in the GitHub repository TonyWu20/fortran-dev-pipeline (5 stars, last pushed 4mo ago), licensed MIT. It adds 82 tokens to every session and 1,250 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…