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.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.00068 | $0.01716 |
| Opus 5 | $0.00034 | $0.00858 |
| Sonnet 5 | $0.00014 | $0.00343 |
| Haiku 4.5 | $0.00007 | $0.00172 |
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 8d 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 — 161 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)
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: 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.
Execution Modes
full (default)
Run the complete pipeline: discover → audit → implement → validate.
discover-only
Run only pseo-discovery. No code changes. Use when the user doesn't yet know what to build.
audit-only
Run pseo-audit and pseo-quality-guard. No code changes. Assumes discovery is done.
implement
Skip discovery and audit, go straight to implementation (assumes both were already done).
validate
Run only pseo-quality-guard against the existing implementation.
Full Pipeline Procedure
Phase 0: Discovery
- Run pseo-discovery with scope
all - Present the discovery report: data assets found, proposed page types, rejected candidates
- Ask the user to confirm which page types to pursue
- If data enrichment is needed, flag it — implementation cannot produce quality pages without sufficient data
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.
- 8d 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 (53 stars, last pushed 7mo ago), licensed MIT. It adds 68 tokens to every session and 1,716 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…