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 JiaWeiXie/swarm-pi-code-plugin --skill swarm-pi-scaffoldgit clone --depth 1 https://github.com/JiaWeiXie/swarm-pi-code-pluginWrote 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/jiaweixie/swarm-pi-code-plugin/swarm-pi-scaffold)<a href="https://agentmods.dev/skills/jiaweixie/swarm-pi-code-plugin/swarm-pi-scaffold"><img src="https://agentmods.dev/badge/skills/jiaweixie/swarm-pi-code-plugin/swarm-pi-scaffold.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.00052 | $0.00442 |
| Opus 5 | $0.00026 | $0.00221 |
| Sonnet 5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
swarm-pi-scaffold 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 8d 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.
What it actually says
Scaffold A Project With Pi
Follow the Skill Control Loop. Load Resource-Aware Execution before expensive or recursive scaffold commands.
- Run
$RUNNER plan --host "$HOST" --role project-architect --prompt-file "$PROMPT_FILE" --execution-mode "$EXECUTION_MODE" --approval-mode "$APPROVAL_MODE" --jsonto draft a version 1ScaffoldSpec. Use the control loop for every non-terminal result. - Require request, project name, target mode, runtime, package manager, structure, dependencies, lifecycle-script policy, observable completion criteria, and sequential verification. Present the complete spec before mutation.
- After explicit approval, run
$RUNNER scaffold --host "$HOST" --role scaffolder --spec-file "$SPEC_FILE" --target "$TARGET" --execution-mode "$EXECUTION_MODE" --approval-mode "$APPROVAL_MODE" --json. - Eligible staging is exact, in-scope, fully reversible, and paired with rollback and verification. Adoption and materialization remain user decisions.
- Add
--adopt-existingonly after the user approves the target inventory andtargetMode: adopt. - Complete only when provenance, changed files, and fresh verification satisfy
the approved spec. After explicit approval, materialize only a
deliverable: trueartifact through$RUNNER jobs materialize --job <id> --target "$TARGET" --json.
The trusted control plane owns target fencing, staging metadata, the initial artifact commit, and materialization; Pi produces the staged artifact.
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.
- 8d ago First seen · 30 lines · 52 tokens per session scan A e6555997de4a
swarm-pi-scaffold is a skill published in the GitHub repository JiaWeiXie/swarm-pi-code-plugin (2 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 442 once invoked, about $0.0003 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
review-team
A multi-reviewer code review process that checks a change from several specialist viewpoints and combines the results into one report. It can cover bugs, security, tests, dependencies, frontend behavior, and continuous-integration workflows.
panel
Convenes a blind Codex and Grok panel on one neutral brief and adjudicates the verdicts.
ultra
Fans the work out as a fleet of parallel Grok and Codex agents billed to their own subscriptions, then synthesizes one result. The peer engine equivalent of ultracode, adding intensity without spending Claude quota on the fleet. Use it for genuinely broad goals, not only explicit asks for intensity.
grok-prompting
Brief writing guidance for composing self contained Grok briefs for coding, review, diagnosis, and second opinion tasks.
grok-result-handling
Internal guidance for presenting Grok companion output back to the user.
smoke
Runs a three probe live smoke wave after a plugin update and reports gate chain health before real work rides it.