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 agentmods add skills/dork-labs/dorkos/creating-pull-requestsnpx skills add dork-labs/dorkos --skill creating-pull-requestsgit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/creating-pull-requests)<a href="https://agentmods.dev/skills/dork-labs/dorkos/creating-pull-requests"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/creating-pull-requests.svg" alt="Measured on agentmods" 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 | $0.00084 | $0.08840 |
| Opus 5 | $0.00042 | $0.04420 |
| Sonnet 5 | $0.00017 | $0.01768 |
| Haiku 4.5 | $0.00008 | $0.00884 |
Grade C, and why
creating-pull-requests scanned grade C with 1 finding 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 yesterday.
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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- The double quotes are load-bearing: verbatim what the post-commit hook writes. Prettier rewrites quotes inside an embedded fence, hence the ignore. --> How it starts
The opening of the file, as written. The whole thing — 657 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Pull Requests
How DorkOS PRs are opened and how the automated Claude review behaves on them. This repo is routinely multi-agent, so the mechanics below keep PRs clean and the review loop cheap.
When to use
- You have finished a branch and are deciding when to open the PR.
- You are about to open a PR (from an agent or by hand).
- A PR already has review feedback and you want another pass once it is addressed.
- You want to dial a PR's review up, down, or off.
The order: review the branch, then open the PR
The independent adversarial review runs against a pushed branch, before a PR exists. Opening the PR is the last step, not the first:
- Build in an isolated worktree and run the local gates.
- Push the branch. Open nothing.
- A reviewer fetches and checks out that branch. It does not need a PR.
- Findings, fixes, convergence.
- Squash to one clean commit carrying one changelog fragment.
- Then open the PR, already reviewed, so the repo's automated review spends its single pass on final content.
Every reason below is a cost measured on 2026-07-27/28, not a preference:
- Merge churn. A PR held open across review rounds watches
mainmove under it. One night of that took roughly a dozengh pr update-branchcalls and still left aDIRTYPR needing a semantic conflict resolved by hand. - The changelog gate. A fragment claims the commits that existed when it was
written. Review-fix commits arrive afterwards uncovered, and
fragment-presentfails. Three PRs failed this way in one night. One commit and one fragment removes the failure mode instead of working around it. - An open PR is an invitation to act. Another session armed auto-merge on a PR carrying two open blocking findings. Both were browser-only and untested, so every check was green with the defects live. A branch invites nothing.
- The automated review fires on open, so opening early spends it on a draft.
The one real cost: CI does not run until the PR opens. Cover it two ways. Run
the local gates yourself, which is cheap (pnpm verify, plus the changelog gate
below). And when a runner-only check is the honest gate (smoke tests, the packaged
runtime, Docker, anything path-filtered to its own workflow), open a draft so
CI runs without inviting a merge, then mark ready once review converges.
What ships with it
2 files 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.
- yesterday Changed · +17 lines 5945f805ceb3
- 5d ago First seen · 640 lines · 84 tokens per session scan C ce3d4f212428
creating-pull-requests is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 8,840 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-pagerank-analyzer
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.
agent-neural-network
Agent skill for neural-network - invoke with $agent-neural-network.
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).