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 skills add CodeInfinity1/Stram --skill github-pr-workflowgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/github-pr-workflow)<a href="https://agentmods.dev/skills/codeinfinity1/stram/github-pr-workflow"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/github-pr-workflow/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/codeinfinity1/stram/github-pr-workflow"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/github-pr-workflow.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.00037 | $0.00631 |
| Opus 5.5 | $0.00015 | $0.00252 |
| Sonnet 5.5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
github-pr-workflow 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR Workflow
Purpose
Support branch-to-PR delivery while protecting worktree state and user changes. This skill uses local Git/gh through native shell tooling when configured.
When To Use
Use for creating branches, committing, pushing, opening PRs, checking PR status, inspecting CI, or preparing merge-ready summaries.
Inputs And Evidence
- Repo root, branch, remote, diff, commits, PR URL/number, CI checks, and user approval.
- Current worktree status and verification output.
Tool Map
github_pr_packet_creategithub_repo_state_report_creategithub_artifact_inspectci_failure_report_createapproval_policy_review_createrun_shell_commandread_filesearch_workspacewrite_notecode-reviewci-failure-debugging
Workflow
- Confirm repo root and worktree status.
- Protect unrelated dirty changes.
- Use
github_repo_state_report_createto record branch, status, changed files, recent commits, verification evidence, and known risk when a durable handoff is useful. - Run appropriate tests or diff checks before commit when feasible.
- Commit intentionally with scoped files.
- Use
github_pr_packet_createto prepare a local PR packet with summary, changes, verification, CI checks, review notes, and risks. - Inspect the packet with
github_artifact_inspectbefore posting, pushing, or handing off. - Push only when the user requested it.
- Open or inspect PR with
ghonly when configured and approved. - Report PR URL, branch, checks, and remaining risk.
Native Implementation Boundaries
- Use native Stram GitHub packets for summaries and repo-state handoffs.
- Use native shell/Git/gh commands through Stram tooling or the current Codex environment only for live Git operations.
- Do not import external reference GitHub workflow scripts.
- Do not use upstream GitHub helpers as runtime implementation.
Safety And Approval
- Pushing, merging, rebasing shared branches, or deleting branches requires explicit user intent.
- Never reset or discard user changes without explicit instruction.
- Do not include secrets in commits or PR text.
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 · 78 lines · 37 tokens per session scan A d4c4407c7a5c
github-pr-workflow is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 631 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
pr-review-fix-pipeline
Reviews a PR and applies fixes for the non-controversial findings: review, fix, test, and commit in one pass. Writes code, so use it only on feature branches where automatic edits are fine. Trigger on: "review and fix PR", "auto-fix the PR", "review PR #X and fix issues", "run the review pipeline".
contribute
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step.
ship
Review changed files with your project's review skill, fix findings, and commit; deploy with --deploy.
eg-precommit-review
Run a Codex-native pre-commit independent-review loop on pending changes.
commit-review
Review git commits for quality, clarity, and best practices before pushing. Checks commit message format, diff size, test coverage signals, and common mistakes. Use when reviewing commits, before pushing, when asked to "check my commits", "review changes", or "is this ready to push".