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 soulcodex/agentic --skill new-gh-issue-orchestrationgit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/new-gh-issue-orchestration)<a href="https://agentmods.dev/skills/soulcodex/agentic/new-gh-issue-orchestration"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/new-gh-issue-orchestration/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/soulcodex/agentic/new-gh-issue-orchestration"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/new-gh-issue-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01038 |
| Opus 5 | $0.00027 | $0.00519 |
| Sonnet 5 | $0.00011 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
new-gh-issue-orchestration 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 9d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New GitHub Issue Orchestration Skill
Trigger Contract
Use this skill when the user input matches one of these patterns:
new-gh-issue: https://github.com/<org>/<repo>/issues/<number>new-gh-issue: <number>
Important:
new-gh-issue:is a workflow trigger phrase, not a shell command.- Never try to execute
new-gh-issuein a terminal. - Parse the value after
new-gh-issue:as issue identifier input.
Step 1 - Preflight Checks
Run:
git status --short
git branch --show-current
Rules:
- If working tree is dirty, stop and ask whether to stash/commit before proceeding.
- If issue identifier is missing/invalid, ask for a valid GitHub issue URL or number.
Step 2 - Resolve Issue Context
Run:
gh issue view <issue> --repo <owner>/<repo> --comments
Extract:
- issue title, number, and intent
- implementation constraints
- any prior planning comments
Step 3 - Create Proper Branch from Rebased Main
Run:
git checkout main
git fetch origin main
git rebase origin/main
git checkout -b <type>/<issue-number>-<scope-slug>
Branch naming rules:
- Use Conventional Commit type prefix (
feat/,fix/,docs/,chore/). - Include issue number and short kebab-case slug from issue scope.
Step 4 - Reviewer-First Analysis
Delegate to reviewer agent to:
- identify scope risks and blockers
- tighten file-level boundaries
- produce a worker-ready checklist
If reviewer finds blocking ambiguity, resolve it before coding.
Step 5 - Worker Agent Execution
Delegate to worker with reviewer-constrained checklist:
- implement requested scope
- run required validations
- report changed files and tradeoffs
Step 6 - Reviewer Agent Validation Gate
After worker delivery, delegate to reviewer agent for a second-pass validation gate.
Loop policy:
- Maximum automatic iterations: 3.
- If reviewer reports no blocking findings, proceed.
- If reviewer reports blocking findings:
- acknowledge the developer with a concise findings summary
- if mitigation is possible, in-scope, and absolutely needed, pass a mitigation plan back to worker
- after worker fixes, run reviewer again
- If still unresolved after 3 automatic iterations, stop and ask developer for clear next instructions.
What ships with it
1 file 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.
- 9d ago First seen · 158 lines · 54 tokens per session scan A 5896295f0ac3
new-gh-issue-orchestration is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 1,038 once invoked, about $0.0003 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
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
atmos-vendoring
Component vendoring: vendor.yaml and component.yaml manifests, immutable vendor.lock.yaml receipts, pulling from Git/S3/HTTP/OCI/Terraform Registry, --stack/--labels/--tags selector composition, native vendor update, clean, diff, config, and reviewed local component copies.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims, signed commits, managed workdirs, fork-PR trust gate, and auth via identities or github/sts.
hatch3r-issue-workflow
Guides the 8-step agentic development workflow for issues/work items. Covers parsing issues, loading skills, reading specs, planning, implementing, testing, opening PRs/MRs, and addressing review. Use when working on any issue/work item or when the user mentions an issue number.