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/statusgit 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/status)<a href="https://agentmods.dev/commands/generous-corp/pulp/status"><img src="https://agentmods.dev/badge/commands/generous-corp/pulp/status.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.00013 | $0.00374 |
| Opus 5 | $0.00006 | $0.00187 |
| Sonnet 5 | $0.00003 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
status 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
Show the current project status.
Always start by printing the canonical version line so "what Pulp am I using?" is answered on every /status invocation:
Claude plugin <plugin_version> · Pulp SDK/CLI <sdk_version>
See .claude/commands/version.md for the exact parsing recipe. Reuse the same logic — do not reinvent it.
Then run: pulp status when the CLI is on PATH, or ./build/pulp status from a source build.
In a Pulp source checkout, include the PR workflow lines from pulp status
when reporting status; they show whether this checkout is using Shipyard,
direct gh, or manual PR handling.
Also include the Import design defaults: line from pulp status when
present; it shows whether pulp import-design will default to live JS,
baked DesignIR, or baked C++, and whether that came from built-ins, config,
or environment overrides.
Include the Control broker: line. Treat unavailable as nonfatal and
reachable-unverified only as evidence that a local carrier accepted a
connection. Without a trusted peer expectation, never paraphrase that state as
healthy or verified. The status probe is observational and must not be followed
by starting or repairing a broker unless the user separately asks for mutation.
If the CLI binary doesn't exist, fall back to showing:
git status— current branch and changesgit log --oneline -5— recent commitsls build/— whether a build directory existscat docs/status/support-matrix.yaml | head -40— format support status
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 · 35 lines · 13 tokens per session scan A ec57636ef069
status is a command published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 374 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.