Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/d-oit/rust-2026-templatenpx agentmods add skills/d-oit/rust-2026-template/stacked-prsWrote 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/d-oit/rust-2026-template/stacked-prs)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/stacked-prs"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/stacked-prs/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/d-oit/rust-2026-template/stacked-prs"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/stacked-prs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 118 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00072 | $0.01230 |
| Opus 5.5 | $0.00029 | $0.00492 |
| Sonnet 5.5 | $0.00014 | $0.00246 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
stacked-prs 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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stacked PRs (Optional)
When to Use
Stacked PRs are OPTIONAL. Default to single-PR atomic commits (see atomic-commit skill).
Use stacks ONLY when ALL of these hold:
- Feature has 3+ distinct concerns with clear dependencies
- Different layers need different reviewers
- Bottom layers can merge independently while top layers are WIP
- Repository is on GitHub (not GitLab)
Do NOT use for: bug fixes, hotfixes, small/medium changes, or issue-triage batch work.
Setup
gh extension install github/gh-stack
git config rerere.enabled true # remember conflict resolutions
See https://github.com/github/gh-stack for the full agent skill (SKILL.md + references/). This file provides template-specific integration guidance only.
Decision Flow
Use stacked PRs when: GitHub repo, 3+ distinct layers, different reviewers per layer.
Otherwise: use atomic-commit (single PR).
Template Integration
- Quality gates run per-PR naturally — each layer gets its own CI via
./scripts/quality-gates.sh - Conventional commits per layer:
feat(scope): description - Branch naming:
<topic>/<concern>(e.g.,billing/schema,billing/api) - Metrics: Report one event per layer completion to
.agents/events/YYYY/MM/DD/ - Hotfixes: Never stack hotfixes — they must be atomic for DORA Change Failure Rate tracking
Non-Interactive Agent Usage
Always use flags to avoid TUI blocking:
| Command | Use | Never run bare |
|---|---|---|
| View | gh stack view --json |
gh stack view (opens TUI) |
| Submit | gh stack submit --auto |
gh stack submit (prompts per PR) |
| Submit (ready) | gh stack submit --auto --open |
creates non-draft PRs |
| Init | gh stack init <branches...> |
gh stack init (prompts for names) |
| Merge | gh stack merge <pr-number> --yes |
gh stack merge (interactive picker) |
| Add | gh stack add <branch> |
gh stack add (prompts for name) |
| Checkout | gh stack checkout <target> |
gh stack checkout (opens menu) |
| Modify | Not available non-interactively | gh stack modify (TUI-only) |
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.
- 1mo ago Changed · +1 lines 19f02e7024ec
- 2mo ago First seen · 121 lines · 72 tokens per session scan A 4a923783f3ff
stacked-prs is a skill published in the GitHub repository d-oit/rust-2026-template (14 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 1,230 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-31.
Other skills, from other repositories
fix-issue
Fixes a bug, implements a missing feature, or implements one slice of a larger feature, starting from a GitHub issue link, number, or direct text description. Trigger when the user gives a GitHub issue URL/reference/description and asks to fix, implement, resolve, or work on it.
rust-check
Run cargo check on the current Rust project to find compile errors.
moli-webfetch
Fetch, inspect, crawl, and capture live, JavaScript-rendered websites with Moli. Use when Codex needs current web content, web research, fact lookup, link following, a bounded crawl, client-rendered or response-gated content, network diagnostics, or a standalone HTML, Markdown, JSON, semantic-tree, viewport or…
LifeOSHooks
The LifeOS function-hook plugin: check it is armed, explain why a line or banner was or was not drawn, regenerate its types after a Claude Code update, sync pure-core copies, run its probes. USE WHEN function hooks, LifeOSHooks, the plugin, hook-drawn lines, banner missing, memory line missing, plugin types…
RootCauseAnalysis
Structured incident investigation using Five Whys, Fishbone, blameless Postmortem, Fault Tree, Kepner-Tregoe, and FMEA — traces failures to systemic root causes rather than blaming humans. USE WHEN root cause, RCA, 5 whys, fishbone, postmortem, incident analysis, fault tree, why does this keep failing, blameless…
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.