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/ivo-toby/postgram/speckit.plangit clone --depth 1 https://github.com/ivo-toby/postgramWrote 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/ivo-toby/postgram/speckit.plan)<a href="https://agentmods.dev/commands/ivo-toby/postgram/speckit.plan"><img src="https://agentmods.dev/badge/commands/ivo-toby/postgram/speckit.plan.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.00014 | $0.00787 |
| Opus 5 | $0.00007 | $0.00394 |
| Sonnet 5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
speckit.plan 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 6d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 6d ago First seen · 91 lines · 14 tokens per session scan A f57498330b6b
speckit.plan is a command published in the GitHub repository ivo-toby/postgram (7 stars, last pushed 2d ago), licensed AGPL-3.0. It adds 14 tokens to every session and 787 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-31.
Other commands, from other repositories
gsd:profile-user
Generate developer behavioral profile and create Claude-discoverable artifacts.
gsd:resume-work
Resume work from previous session with full context restoration.
gsd-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
deja
Search this machine's past AI coding sessions (deja-vu).
brain
The brain is what you have read and kept: a folder of Markdown that px0 ingests into, indexes, and answers questions from. It can be px0's own brain/ folder or any folder of Markdown you already keep — including an Obsidian vault.
tools
Tools are the external app actions a workflow may call — send a Slack message, open a Linear issue, read a Google Sheet. Every toolkit currently routes through Composio, which brokers the authorization.