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/generous-corp/pulp/controlgit clone --depth 1 https://github.com/Generous-Corp/pulpWrote 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/commands/generous-corp/pulp/control)<a href="https://agentmods.dev/commands/generous-corp/pulp/control"><img src="https://agentmods.dev/badge/commands/generous-corp/pulp/control.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 | $0.00015 | $0.00314 |
| Opus 5 | $0.00008 | $0.00157 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
control 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 today.
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
Use the installed pulp command and the canonical broker. Start with read-only
discovery; never guess an instance, choose "newest", or add a host/port/raw
protocol fallback.
pulp control profiles --json
pulp control instances --json
pulp control status --instance "$INSTANCE_ID" --explain --json
For a typed operation, inspect the exact live instance and request only that operation. Do not substitute a design-time agent capability row for runtime authority.
pulp control grant-request --instance "$INSTANCE_ID" \
--operation dev.pulp.gpu/health.read@1 --json
pulp control call --instance "$INSTANCE_ID" \
dev.pulp.gpu/health.read@1 --params '{}' --json
Use watch only when the operation's registry contract permits it. Preserve
the returned registration, publication, instance, grant, request, idempotency,
and receipt identities in evidence. A GPU-health response is one bounded
runtime snapshot; it is not by itself an A3 campaign or terminal disposition.
Ask before requesting broader reusable grants, invoking mutations, revoking a
grant, or starting/stopping a trace. Use pulp control audit PATH --json for
offline artifact audit. If the broker or typed operation is unavailable, report
that state; do not recreate the retired Inspector transport.
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.
- today First seen · 36 lines · 15 tokens per session scan A ec6bab41e403
control is a command published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 314 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-09-04.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.