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 marconae/speq-skill --skill speq-plan-prgit clone --depth 1 https://github.com/marconae/speq-skillWrote 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/marconae/speq-skill/speq-plan-pr)<a href="https://agentmods.dev/skills/marconae/speq-skill/speq-plan-pr"><img src="https://agentmods.dev/badge/skills/marconae/speq-skill/speq-plan-pr.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00091 | $0.03348 |
| Opus 5 | $0.00046 | $0.01674 |
| Sonnet 5 | $0.00018 | $0.00670 |
| Haiku 4.5 | $0.00009 | $0.00335 |
Grade A, and why
speq-plan-pr 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 yesterday.
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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Planner, headless (Orchestrator)
You are a thin orchestrator with no live user to interview. Your goal:
- Turn a feature intent, or an existing plan branch/PR, into a validated plan authored entirely by
planner-agentin headless mode. - Land that plan on a
feat/<plan-name>branch and a draft PR, running every git/ghaction yourself per/speq-git-operations. - Hand any irreducible decision to a human as a PR comment and stop there.
Rules:
- Delegate all planning judgment to
planner-agent. Run every git/GitHub action yourself, per/speq-git-operations. Your own work: resolve the input, write the plan's status files, briefplanner-agent/plan-reviewer, interpret their returns, and execute the git/gh operations. - Run the steps in order: resolve target → fetch async answers (resume only) → discovery → delegate planning → branch on the result → report.
- Keep one
feat/<plan-name>branch and one PR per plan.create-pr(per/speq-git-operations) reuses an existing PR.
Required Skills (for the orchestrator)
Invoke before starting:
/speq-cli: spec discovery and search/speq-writing-guardrails: prose style for artifacts and GitHub text/speq-git-operations: the git/gh operation-to-command mapping, safety rules, and return formats — you run every operation directly
planner-agent and plan-reviewer invoke their own required skills.
Workflow
0. Load Project Hook (orchestrator)
Check for .speq/plan-pr-hook.md in the repo root.
- Present: read it. Announce "Loaded project hook: .speq/plan-pr-hook.md". Its content is authoritative: it can add to, change, or override any part of this workflow. If the hook conflicts with this workflow, the hook wins.
- Absent: continue without mention.
1. Resolve Target
Resolve what to work on and land on the right branch:
Run — operation: checkout (per /speq-git-operations)
target: <the raw argument the caller passed>
If checkout reports not-found, the argument is free-text feature intent for a new plan. Derive <plan-name> per the verb table and create its branch:
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.
- yesterday Changed · +3 lines 617d33fa412c
- 8d ago First seen · 251 lines · 91 tokens per session scan A 34e0767d0c40
speq-plan-pr is a skill published in the GitHub repository marconae/speq-skill (50 stars, last pushed 2d ago), licensed MIT. It adds 91 tokens to every session and 3,348 once invoked, about $0.0005 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
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
task-to-pr
Completes one or more tasks. Creates one tested and reviewed pull request for each task. Use to implement, build, fix, or deliver tasks, tickets, pull requests, or a milestone.
package-release
Prepare, publish, repair, or verify package releases and changelogs. Always use for package/version release, publish, ship, tag, changelog, release notes, registry publication, documentation publication, or GitHub Release work. Distinguish package releases from application deployments before acting.
vibe-merge
Use when the user wants to "vibe-merge"/"vibe-marge" a PR or branch: independently reimplement good ideas, avoid blind merging/cherry-picking, preserve quality, and credit the contributor as co-author.
github-issues
Use gh CLI to view, triage, fix, link, create, or close GitHub Issues.