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.
git clone --depth 1 https://github.com/popiliadam/platinum-seo-engineWrote 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/popiliadam/platinum-seo-engine/pseo-schedule)<a href="https://agentmods.dev/commands/popiliadam/platinum-seo-engine/pseo-schedule"><img src="https://agentmods.dev/badge/commands/popiliadam/platinum-seo-engine/pseo-schedule/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/popiliadam/platinum-seo-engine/pseo-schedule"><img src="https://agentmods.dev/badge/commands/popiliadam/platinum-seo-engine/pseo-schedule.svg" alt="Reviewed on agentmods" width="80" 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.00328 | $0.03757 |
| Opus 5 | $0.00164 | $0.01878 |
| Sonnet 5 | $0.00066 | $0.00751 |
| Haiku 4.5 | $0.00033 | $0.00376 |
Grade B, and why
pseo-schedule 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
ENGINE_ROOT="${CLAUDE_PLUGIN_ROOT:-${PSEO_ENGINE_ROOT:-$(find /Users/apple/.claude/plugins/cache 2>/dev/null -type d -name 'platinum-seo-engine' | sort | tail -1 | xargs -I{} find {} -maxdepth 1 -type d -name '[0-9]*' 2> 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.
- 9d ago First seen · 197 lines · 328 tokens per session scan B 48ef4a151f43
pseo-schedule is a command published in the GitHub repository popiliadam/platinum-seo-engine (25 stars, last pushed 27d ago), licensed AGPL-3.0. It adds 328 tokens to every session and 3,757 once invoked, about $0.0016 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
factory-next
Recommend and optionally run the next factory stage for this repo.
reflect
Reflect on recent work — log lessons to the journal and propose distilled rule updates for review.
doctor
Check vault health — broken links, orphans, missing frontmatter, MISSING placeholders — and propose fixes.
install
Guided setup for a new Cowork workspace. Interviews you (about 5 minutes) and generates a full, pre-configured cowork-os workspace (folders, copy, project instructions, and recurring routines).
knowledge-transfer
Interview a person to capture their operating know-how (tacit knowledge) and write it into the workspace as the company brain: processes, rules with source, glossary, decisions and open questions. For onboarding, a key person leaving, or standardizing a process.