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 commands/synaptic-labs-ai/pact-plugin/bootstrapgit clone --depth 1 https://github.com/Synaptic-Labs-AI/PACT-PluginWhat 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.00024 | $0.02186 |
| Opus 5 | $0.00012 | $0.01093 |
| Sonnet 5 | $0.00005 | $0.00437 |
| Haiku 4.5 | $0.00002 | $0.00219 |
Grade A, and why
bootstrap 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session-Start Ritual
The persona body's §2 Session-Start Ritual is your invocation contract; this command holds the mechanical detail. Execute the steps below in order, substituting Session Placeholder Variables from your context.
Step 1 — Identify the session team
Read team_name from the Current Session block in the project's CLAUDE.md (preferred location: $CLAUDE_PROJECT_DIR/.claude/CLAUDE.md; legacy fallback: $CLAUDE_PROJECT_DIR/CLAUDE.md). The session_init hook writes this block at session start.
The platform manages exactly one team per session, named {team_name} — it is provisioned automatically; you do not create it (the TeamCreate/TeamDelete tools no longer exist). Use {team_name} for every specialist dispatch.
Team-config expectations (bidirectional): on resume, a PRESENT team config is reused — never re-create it. An ABSENT config is the NORM after a clean session end — the platform provisions the session team; both states are normal, neither is corruption. Ghost-detection: if a spawn or send fails with a team-not-found error, do NOT blind-retry Agent() — the platform spawn is non-atomic and the process may already be running. Check for inbound messages from the "failed" agent name first; re-spawn only if it stays silent.
Step 2 — Spawn pact-secretary
Spawn the session secretary using single-task dispatch — the pact-secretary agentType is exempt from the teachback gate. No Task A teachback round-trip.
TaskCreate(subject="secretary: deliver session briefing", description="<full mission: deliver session briefing on spawn, answer memory queries during the session, process HANDOFFs at workflow boundaries; CONTEXT / MISSION / INSTRUCTIONS / GUIDELINES per the orchestrator persona §13 Recommended Agent Prompting Structure>")— single work task. The subject names a discrete deliverable (the briefing), NOT the secretary's standing role; the standing duties (memory queries, HANDOFF harvest) live in the description as mission context and are tracked by their own later tasks.TaskUpdate(task_id, owner="secretary")— assign to the secretary; noaddBlockedBy(no teachback gate)Agent(name="secretary", team_name="{team_name}", subagent_type="pact-secretary", description="Spawn session secretary", prompt="YOUR PACT ROLE: teammate (secretary).\n\nYou are joining team {team_name}. As your FIRST action, Invoke Skill(\"PACT:pact-team-registration\") to record your identity. Then checkTaskListfor tasks assigned to you.")- Use
subagent_type="pact-secretary"and the canonicalname="secretary"— the literal name is load-bearing.
- Use
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 · 80 lines · 24 tokens per session scan A 4a769f5c79d6
bootstrap is a command published in the GitHub repository Synaptic-Labs-AI/PACT-Plugin (71 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 2,186 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.