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/validategit 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/validate)<a href="https://agentmods.dev/commands/generous-corp/pulp/validate"><img src="https://agentmods.dev/badge/commands/generous-corp/pulp/validate.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.00008 | $0.00384 |
| Opus 5 | $0.00004 | $0.00192 |
| Sonnet 5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade B, and why
validate scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
If `pulp validate` aborts with "broken code signature", run: `pulp doctor --validators --fix` to clean up user-owned copies (root-owned copies print a sudo one-liner instead of auto-elevating). What it actually says
Run plugin format validation on built plugins.
Use pulp validate when the CLI is on PATH, or ./build/pulp validate from
a source build. Forward any arguments after validate.
This runs available validators:
- auval — Audio Unit validation (macOS, if installed)
- clap-validator — CLAP plugin validation (if installed)
- pluginval — VST3 validation (if installed)
- AAX Validator — AAX validation on macOS/Windows (if installed)
- vstvalidator — optional Steinberg VST3 validator when
--allis passed
Common invocations:
pulp validate
pulp validate --strict
pulp validate --all --json --report validation-report.json
pulp validate --screenshot
pulp validate --target standalone ./build/MyApp.app
If $ARGUMENTS is non-empty, forward it verbatim:
pulp validate $ARGUMENTS
Before launching any validator, pulp validate runs a discovery preflight.
If any validator has a broken code signature (e.g. a copy of pluginval
ripped out of its .app bundle, where amfid will SIGKILL the process at
launch with exit 137 and zero stderr), pulp validate aborts with the exact
path and remediation instead of letting the run die mid-validation.
If no validators are installed, run: pulp doctor --validators to confirm and see install commands.
If pulp validate aborts with "broken code signature", run: pulp doctor --validators --fix to clean up user-owned copies (root-owned copies print a sudo one-liner instead of auto-elevating).
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 · 40 lines · 8 tokens per session scan B f5bbc09499e9
validate is a command published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 384 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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.