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 skills add lisbeth718/pseo-skills --skill pseo-orchestrategit clone --depth 1 https://github.com/lisbeth718/pseo-skillsWrote 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/skills/lisbeth718/pseo-skills/pseo-orchestrate)<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-orchestrate"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-orchestrate/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/skills/lisbeth718/pseo-skills/pseo-orchestrate"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-orchestrate.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.00068 | $0.02225 |
| Opus 5.5 | $0.00027 | $0.00890 |
| Sonnet 5.5 | $0.00014 | $0.00445 |
| Haiku 4.5 | $0.00007 | $0.00222 |
Grade A, and why
pseo-orchestrate 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pSEO Orchestrator
Coordinate the execution of all pseo-* skills in the correct dependency order to implement or validate a complete programmatic SEO system.
Skill Dependency Graph
pseo-discovery (0) ← what should we build? what data exists?
│
▼
pseo-audit (1) ← is the codebase ready for what we want to build?
│
▼
pseo-scale (1.5) ← CONDITIONAL: only if 10K+ pages planned
│
▼
pseo-data (2)
│
├──────────────┐
▼ ▼
pseo-templates (3) pseo-linking (4)
│ │
└──────┬───────┘
│
┌──────┴───────┐
▼ ▼
pseo-metadata (5) pseo-schema (6) ← parallel: both read from data layer
│ │
└──────┬───────┘
│
┌──────┴───────┐
▼ ▼
pseo-performance pseo-llm-visibility ← parallel: independent optimizations
(7) (8)
│ │
└──────┬───────┘
▼
pseo-quality-guard (9)
│
▼
gsc (10) ← post-launch monitoring (after pages are live)
Note: metadata and schema are independent of each other - both read from the data layer and render into templates. Run them in parallel in Phase 4.
Note: gsc is a post-launch step. It needs live pages and a submitted sitemap, so it runs after deployment and then on a recurring schedule, not inside the build.
Note: the general SEO skills sit beside this pipeline: seo-i18n runs with Phases 3-4 when the site is multilingual (alongside pseo-linking and pseo-metadata), seo-regression-guard runs before and after each deploy, seo-log-analysis and seo-content-refresh run after launch with gsc, and seo-migration is standalone (URL, domain or stack changes).
Note: pseo-scale only applies when discovery identifies 10K+ pages. It runs after audit to set up database infrastructure, data sufficiency gating, and CDN architecture before the data layer is built. At < 10K pages, skip it entirely.
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 Changed · +1 lines 381a215c5390
- 26d ago Changed · +17 lines 3b31ecee089d
- 2mo ago First seen · 161 lines · 68 tokens per session scan A cda3bd96ae58
pseo-orchestrate is a skill published in the GitHub repository lisbeth718/pseo-skills (55 stars, last pushed 9d ago), licensed MIT. It adds 68 tokens to every session and 2,225 once invoked, about $0.0003 per session on Opus 5.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.
pseo-orchestrate compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pseo-orchestratelisbeth718/pseo-skills | Skill | 55 | 9d ago | MIT | A | 68 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |