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-content-decay)<a href="https://agentmods.dev/commands/popiliadam/platinum-seo-engine/pseo-content-decay"><img src="https://agentmods.dev/badge/commands/popiliadam/platinum-seo-engine/pseo-content-decay/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-content-decay"><img src="https://agentmods.dev/badge/commands/popiliadam/platinum-seo-engine/pseo-content-decay.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.00227 | $0.01185 |
| Opus 5 | $0.00113 | $0.00593 |
| Sonnet 5 | $0.00045 | $0.00237 |
| Haiku 4.5 | $0.00023 | $0.00119 |
Grade A, and why
pseo-content-decay 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 10d 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.
- 10d ago First seen · 53 lines · 227 tokens per session scan A eeca3f5dce0d
pseo-content-decay is a command published in the GitHub repository popiliadam/platinum-seo-engine (25 stars, last pushed 29d ago), licensed AGPL-3.0. It adds 227 tokens to every session and 1,185 once invoked, about $0.0011 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-30.
Other commands, from other repositories
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.
react-router-client-loader
Do this in a clientLoader and use loaderData to render the component. DO NOT create mock data, new interfaces, or mock data loader functions. Instead, assume loaderData has all of the data you need to render the component.