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 priyanshuchawda/codeaudit --skill github-issue-pr-workflowgit clone --depth 1 https://github.com/priyanshuchawda/codeauditWrote 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/priyanshuchawda/codeaudit/github-issue-pr-workflow)<a href="https://agentmods.dev/skills/priyanshuchawda/codeaudit/github-issue-pr-workflow"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/codeaudit/github-issue-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/priyanshuchawda/codeaudit/github-issue-pr-workflow"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/codeaudit/github-issue-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.00210 |
| Opus 5.5 | $0.00015 | $0.00084 |
| Sonnet 5.5 | $0.00007 | $0.00042 |
| Haiku 4.5 | $0.00004 | $0.00021 |
Grade A, and why
github-issue-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.
What it actually says
GitHub Issue PR Workflow
Required Flow
- Create or propose an issue first.
- Use a clean scoped branch.
- Keep commits focused and descriptive.
- Link the PR to the issue.
- List tests run.
- Describe security impact and docs impact.
- Merge only after clean review and verification.
Branch Names
fix/issue-12-api-rate-limitrefactor/issue-18-split-security-utilsdocs/issue-21-evidence-map
PR Body Sections
- Linked issue
- Summary
- Tests run
- Security impact
- Docs impact
- Screenshots when UI changed
No auto-push, branch deletion, remote mutation, or auto-merge without explicit user approval.
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 · 36 lines · 37 tokens per session scan A b8e58f3f861e
github-issue-pr-workflow is a skill published in the GitHub repository priyanshuchawda/codeaudit (1 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 210 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-08-31.
Other skills, from other repositories
papi-build
Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.
papi-auto
Continue an approved PAPI cycle through implementation, verification and review using bounded autonomy. Resume durable work without rebuilding it; propose new scope before persisting it.
pn-github-vertical-slices
Break a plan or PRD into tracer-bullet vertical slices and create GitHub Issues via GitHub MCP (official github/github-mcp-server). Dependencies first (AFK/HITL). Use after pn-writing-plans or pn-create-prd when work must ship as Issues.
github
GitHub patterns using gh CLI for pull requests, stacked PRs, code review, branching strategies, and repository automation. Use when working with GitHub PRs, merging strategies, or repository management tasks.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.