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 Stivi7/cyberpunk-context-runners --skill worktree-isolationgit clone --depth 1 https://github.com/Stivi7/cyberpunk-context-runnersWrote 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/stivi7/cyberpunk-context-runners/worktree-isolation)<a href="https://agentmods.dev/skills/stivi7/cyberpunk-context-runners/worktree-isolation"><img src="https://agentmods.dev/badge/skills/stivi7/cyberpunk-context-runners/worktree-isolation/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/stivi7/cyberpunk-context-runners/worktree-isolation"><img src="https://agentmods.dev/badge/skills/stivi7/cyberpunk-context-runners/worktree-isolation.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.00022 | $0.00519 |
| Opus 5.5 | $0.00009 | $0.00208 |
| Sonnet 5.5 | $0.00004 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
worktree-isolation 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Isolation
Metadata
- Version: 1.0.0
- Triggers: Mutating implementation jobs, sequential or parallel
- Allowed agents: Nexus, Fragmenter, Daemon, Neon, Grid Master
- Side effects: Creates branches, worktrees, internal commits, merges, and local run state
When to Use
Use for every mutating implementation job that may write repository files. The only approved planning-artifact exception is an approved PRD that The Fixer writes and commits by itself on the current named branch after design and artifact approval. This exception does not exempt implementation or unrelated files from worker branch, review, and integration requirements. Read-only planning and review do not need their own worktree.
Inputs
Task id, slug, requested target, approved base commit, role, work unit, allowed scope, dependencies, integration contract, worktree root, runtime isolation capability, and cleanup policy.
Procedure
- Resolve the user-provided integration branch or create
cyberpunk/<task-id>-<slug>from the approved base commit. - Refuse an implicit protected branch or unrelated branch as the integration target.
- Verify a project-local worktree root is ignored.
- Create
cyberpunk/<task-id>/<role>-<work-unit>as the worker branch and give it a dedicated worktree. - Accept a native runtime worktree copy only when it preserves the recorded worker branch, base commit, allowed scope, and integration contract. Otherwise Nexus creates the Cyberpunk worktree before dispatch.
- Record owner, integration branch, worker branch, worktree, base commit, allowed scope, integration contract, dependencies, and status in local run state.
- Run project setup and baseline verification inside the worktree.
- After implementation verification, create an internal worker commit and return its SHA.
- Require Gatekeeper approval before integration.
- Merge approved workers into the integration branch in dependency order and run assembled verification.
- After confirmed integration, perform safe worktree cleanup and apply branch cleanup policy.
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 Changed · +1 lines 40c184c3ac13
- 2mo ago First seen · 43 lines · 22 tokens per session scan A 5a1c2bfde5f0
worktree-isolation is a skill published in the GitHub repository Stivi7/cyberpunk-context-runners (4 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 519 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.