Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gideondk/strata/plugin install strataWrote 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/gideondk/strata/promote-to-pr)<a href="https://agentmods.dev/skills/gideondk/strata/promote-to-pr"><img src="https://agentmods.dev/badge/skills/gideondk/strata/promote-to-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/gideondk/strata/promote-to-pr"><img src="https://agentmods.dev/badge/skills/gideondk/strata/promote-to-pr.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.00116 | $0.00528 |
| Opus 5 | $0.00058 | $0.00264 |
| Sonnet 5 | $0.00023 | $0.00106 |
| Haiku 4.5 | $0.00012 | $0.00053 |
Grade A, and why
strata:promote-to-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 11d 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.
What it actually says
strata:promote-to-pr
Take what just happened in this session, decisions made, files touched, open questions, anything reviewers should see, and post it as a comment on the open PR for the current branch.
This is the deliberate counterpart to the silent pr-context/ notes:
it makes Claude's session visible to everyone watching the PR.
When to use
- After a substantive working session where reviewers should know what changed since their last look.
- To leave a "what's left" handoff before stepping away.
- To answer a reviewer's question with context Claude already gathered.
Not for: every small commit. PR comments accumulate quickly, be selective.
How
User runs /strata:promote-to-pr [--pr N]. You:
- Compose the summary as a focused comment. Markdown, links to commits/ files where useful, no large diffs. Aim for under 800 chars.
- Invoke:
"${CLAUDE_PLUGIN_ROOT}/bin/strata" promote-to-pr --dry-run <<'STRATA_PR_COMMENT'
<summary body>
STRATA_PR_COMMENT
- Read the dry-run output back to the user. They confirm or edit.
- Re-run without
--dry-runto post.
This two-step is on purpose. PR comments are public-ish (visible to Everyone on the PR) and shouldn't be sent on a prompt's say-so.
Targeting a specific PR
If the branch has multiple PRs (rare) or you want to comment on a different
PR, pass --pr <number>.
Failure modes
ghnot installed → script exits 2 with a clear message.ghnot authenticated → same.- No open PR for the branch → exits 2.
- Network error during
gh pr comment→ exits 1, prints the gh error.
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.
- 11d ago First seen · 56 lines · 116 tokens per session scan A 7ff324fc175a
strata:promote-to-pr is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed yesterday), licensed MPL-2.0. It adds 116 tokens to every session and 528 once invoked, about $0.0006 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
orbit-github
Open Orbit briefing skill — selected by the Orbit pipeline when GitHub is the user's only connected connector, or when the user explicitly scopes their daily digest to GitHub. Pulls the past 24 hours of PRs, review requests, issues, CI runs, and merges from the user's authenticated GitHub connection and renders them…
diff-review
Render the patch-edit run's accumulated changes as a reviewable diff, surface it through a GenUI choice surface, and persist the user's accept / reject decision into the artifact manifest.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
pr-reviewer
Fetches PR review comments, analyzes requested changes, implements fixes, commits and pushes the resolution. Use after a reviewer has left comments on an open PR to close the feedback loop efficiently.
conventions-check
Review a pull request's title, description, and scope against the repository's PR conventions.
ghx
Guidance for safe, reliable GitHub CLI workflows across issues, pull requests, and reviews.