Borrowing it
Nothing to install: this file belongs to jovandyaz/knowtis-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jovandyaz/knowtis-app/main/.agents/skills/stacking-prs/SKILL.mdgit clone --depth 1 https://github.com/jovandyaz/knowtis-appWrote 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/jovandyaz/knowtis-app/stacking-prs)<a href="https://agentmods.dev/skills/jovandyaz/knowtis-app/stacking-prs"><img src="https://agentmods.dev/badge/skills/jovandyaz/knowtis-app/stacking-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/jovandyaz/knowtis-app/stacking-prs"><img src="https://agentmods.dev/badge/skills/jovandyaz/knowtis-app/stacking-prs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00068 | $0.00601 |
| Opus 5.5 | $0.00027 | $0.00240 |
| Sonnet 5.5 | $0.00014 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
stacking-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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stacking PRs (GitHub + CodeRabbit)
Knowtis uses GitHub's gh-stack extension for stacked PRs and CodeRabbit for automated first-pass review.
Workflow
- Branch with a Conventional prefix:
feat/<name>,fix/<name>,docs/<name>. - Install the extension once with
gh extension install github/gh-stackifgh stackis unavailable. - Build a tracked stack with
gh stack init <bottom-branch>,gh stack add <next-branch>, andgh stack submit --auto --open, or adopt existing PRs withgh stack link <bottom> … <top>.linktakes PRs or branches bottom-first, creates no local tracking, and only adds membership. - Keep every PR under 100 changed files; CodeRabbit refuses larger reviews. Check with
git diff --name-only <base> <head> | wc -lbefore opening. - Trigger CodeRabbit with
@coderabbitai full reviewand confirm inline comments exist. A green check without comments can mean the review was skipped; fair-usage failures must be retried after the named window. - Address all review feedback before human review.
- Merge with an explicit target, for example
gh stack merge <pr-number> --yes, then rungh stack synclocally. Never manually rebase a stacked branch after GitHub merges and retargets a layer. - Detailed context lives in the PR description; commits stay single-line.
Gotchas
gh stack viewneeds local tracking; afterlink, rungh stack checkout <stack-number>first.gh pr editis broken on this repo (deprecated GraphQL field). Change bases and bodies withgh api repos/<owner>/<repo>/pulls/<n> -X PATCH --input -.- Deleting a branch that is the base of an open PR auto-closes that PR, and GitHub then refuses both a base change and a reopen. Run
gh pr list --base <branch>before deleting anything. - Verify
gh auth statusshows the intended account before every write.
Rules of thumb
- A PR that mixes a refactor with a behavior change should be split into a stack (refactor below, behavior on top).
- Do not merge a middle layer independently; use the stack-aware merge flow.
- CI must be green per-PR;
nx affectedkeeps each stack level cheap.
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 First seen · 34 lines · 68 tokens per session scan A 8850812c52e3
stacking-prs is a skill published in the GitHub repository jovandyaz/knowtis-app (4 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 601 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
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
release-notes
Compare the repository with the team's Folio wiki and write release notes: read git log since the last tag, read the Roadmap table, create or update a Release notes page and add what the roadmap table is missing. Use when asked for release notes or to sync the wiki with the code.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
otto-drive-pr
PR mergeability, CI, and live preview.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…