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-implement-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-implement-pr)<a href="https://agentmods.dev/skills/marconae/speq-skill/speq-implement-pr"><img src="https://agentmods.dev/badge/skills/marconae/speq-skill/speq-implement-pr/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/marconae/speq-skill/speq-implement-pr"><img src="https://agentmods.dev/badge/skills/marconae/speq-skill/speq-implement-pr.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.01925 |
| Opus 5.5 | $0.00030 | $0.00770 |
| Sonnet 5.5 | $0.00015 | $0.00385 |
| Haiku 4.5 | $0.00007 | $0.00193 |
Grade A, and why
speq-implement-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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Implementer, PR flow (Orchestrator)
You are a thin orchestrator on top of speq-implement. Drive a plan on its existing feat/<plan-name> branch to a ready PR through the existing skills, run unchanged:
/speq-implementbuilds and verifies./speq-recordmerges the specs. You run every git/ghaction yourself, per/speq-git-operations.- Record only after the project's real test suites are green.
- Stop on the first failed step and report it. Running the skill again resumes the work.
Required Skills (for the orchestrator)
Invoke before starting:
/speq-cli: spec discovery, to resolve plan names/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
speq-implement and speq-record invoke their own required skills.
Workflow
0. Load Project Hook
Check for .speq/implement-pr-hook.md in the repo root.
- Present: read it. Announce "Loaded project hook: .speq/implement-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
$1 empty → ask the user which plan. Otherwise check out the target (for a bare plan name, that is its feat/<plan-name> branch):
Run — operation: checkout (per /speq-git-operations)
target: <$1: a plan name (→ feat/<plan-name>), PR number, or branch name>
If checkout reports not-found (the plan exists only locally and was never pushed):
Run — operation: create-branch (per /speq-git-operations)
branch: feat/<plan-name>
If specs/_recorded/*-<plan-name>/ exists and specs/_plans/<plan-name>/ does not, the plan is already recorded: skip to step 6.
2. Implement
If verification-report.md exists in the plan directory and every task in tasks.md is [x], skip this step.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · -33 lines · -34 tokens per session 2f5e4145f439
- 12d ago Changed · -10 lines 61e4dd11f42f
- 19d ago Changed · -5 lines dda3eb5c3c39
- 22d ago Changed · +10 lines 5a5b75282678
- 1mo ago Changed · -1 lines 39e6f603c857
- 1mo ago Changed · +31 lines · +31 tokens per session 556d0deacefc
- 1mo ago First seen · 137 lines · 77 tokens per session scan A 9bb3c07a9be4
speq-implement-pr is a skill published in the GitHub repository marconae/speq-skill (55 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 1,925 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.
Other skills, from other repositories
factory
Delivers a spec or decided task through the task-to-pr workflow and merges after all quality and approval gates pass. Explicit invocation grants merge authority for the supplied work.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
verify-before-complete
Block completion claims until verification evidence has been produced in the current message. Use before marking a task/slice/milestone complete, before creating a commit or PR, before saying "it works" or "tests pass", and any time you are about to claim work is done. The rule is: evidence before claims, always …
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.
ship-workflow
Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…