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/wrannaman/agentic-engineering/stack-prnpx skills add wrannaman/agentic-engineering --skill stack-prgit clone --depth 1 https://github.com/wrannaman/agentic-engineeringWhat 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.00000 | $0.00495 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
stack-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.
What it actually says
Stack PR
Create stacked PRs from a plan's PR Stack table.
Purpose
Large features split into small, reviewable PRs that build on each other. This skill creates the stack: branches, draft PRs, and dependency links. Uses plain git + gh CLI — no special tooling required.
Usage
/stack-pr # Create stack from current plan
/stack-pr .plans/2026-03-18-... # Create stack from specific plan
Process
Step 1: Read the PR Stack
From the plan:
| PR | Branch | Steps | Description |
|----|--------|-------|-------------|
| 1 | feat/add-model | 1-2 | User entity and repository |
| 2 | feat/add-api | 3-4 | API endpoints |
| 3 | feat/add-tests | 5-6 | Integration tests |
Step 2: Create Branches
main ← feat/add-model ← feat/add-api ← feat/add-tests
Each branch is based on the previous one.
Step 3: Push and Create Draft PRs
For each branch:
git push -u origin <branch>
gh pr create --base <parent-branch> --head <branch> --draft \
--title "<conventional-commit-title>" \
--body "PR N/M in stack. Depends on #<parent-PR>"
Step 4: Report
Stack created:
PR #101: feat/add-model → main (draft)
PR #102: feat/add-api → feat/add-model (draft)
PR #103: feat/add-tests → feat/add-api (draft)
Merge order: #101 → #102 → #103
After a PR Merges
When PR 1 merges, update PR 2's base:
gh pr edit <PR2> --base main
git checkout feat/add-api && git rebase main && git push --force-with-lease
Use /rebase-fix if conflicts arise.
Hard Rules
- All PRs are drafts — never auto-publish
- Include stack position in title or body ("PR 2/3")
- Link dependent PRs in description
- Merge in order
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 · 74 lines · 0 tokens per session scan A fabab57a8ef3
stack-pr is a skill published in the GitHub repository wrannaman/agentic-engineering (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 495 tokens. 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…