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 agentmods add skills/specsnl/agent-specs/create-prnpx skills add specsnl/agent-specs --skill create-prgit clone --depth 1 https://github.com/specsnl/agent-specsWhat 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 | $0.00067 | $0.00763 |
| Opus 5 | $0.00034 | $0.00381 |
| Sonnet 5 | $0.00013 | $0.00153 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
create-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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Audit the repository's PR configuration, verify CI is green, then open the PR.
Phase 1 — Audit PR requirements
Read the repository's PR configuration before touching git.
1a. Read all workflow files
find .github/workflows -name "*.yml" -o -name "*.yaml" | sort
For each workflow file, identify:
- Jobs triggered by
pull_requestevents - Any title validation steps (e.g.
pr-title-checker,action-semantic-pull-request) - Required status checks that must pass
1b. Check PR title format
Look for .github/pr-title-checker-config.json and read it to extract the allowed prefix pattern.
If not found, check for a workflow step that enforces title format and read its config.
1c. Check branch rules
Read .github/rulesets/*.json if present. Note:
- Required merge method (Specs projects use merge commits only — no squash/rebase)
- Required status checks
1d. Summarise before proceeding
Report:
- What CI jobs will run on this PR
- Required title format / prefix
- Any merge restrictions
Phase 2 — Run CI checks locally
Invoke the ci-green-check skill — it runs whatever checks are discovered in Phase 1 that can run
locally, and hands off to php-checks in Laravel/PHP projects.
Do not proceed to Phase 3 if any check fails.
Phase 3 — Ensure branch and commits are ready
- Confirm the working tree is clean (
git status) - Confirm not on
main/master/develop— if so, create a branch first:
Use the Linear issue slug as the branch name if one was provided.git checkout -b kebab-case-description - Commit messages must be a single subject line — no body, no bullet points.
- Never add a
Co-Authored-Bytrailer or mention Claude in any commit message.
Phase 4 — Create the PR
git push -u origin HEAD
gh pr create --title "PREFIX: short description" --body "$(cat <<'EOF'
## Summary
- ...
EOF
)"
Title rules
- Match the format discovered in Phase 1
- If a Linear issue number was provided:
PREFIX-543: description - If no issue number is available: fall back to
000as the issue number, e.g.PREFIX-000: description. This is the standard fallback — do not ask the user for an issue number when one wasn't provided. DerivePREFIXfrom the title-checker config pattern, or from the prefix used by existing branches/PRs. - Never omit the colon and space after the prefix
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 First seen · 102 lines · 67 tokens per session scan A 7bf804b5dbbc
create-pr is a skill published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 16d ago), licensed MIT. It adds 67 tokens to every session and 763 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.