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/jeremydev87/codingbuddy/plan-to-issuesnpx skills add JeremyDev87/codingbuddy --skill plan-to-issuesgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWhat 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.00057 | $0.02698 |
| Opus 5 | $0.00028 | $0.01349 |
| Sonnet 5 | $0.00011 | $0.00540 |
| Haiku 4.5 | $0.00006 | $0.00270 |
Grade A, and why
plan-to-issues 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 2d 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan to Issues
Convert a completed PLAN into GitHub parent + sub-issues using native sub-issue API.
Follow every step in order. Stop and report if any step fails.
Three Principles
- Independent — Each sub-issue is self-contained. A new session with zero context can start work from the issue alone.
- Deployable — Each sub-issue can be independently branched, PRed, and merged without breaking existing functionality.
- Structured — Issue body has essentials only. Technical details and background go into comments.
Step 1: Determine Plan Source
Check if $ARGUMENTS is provided:
-
With file (
/plan-to-issues docs/plans/my-plan.md): Verify the file exists (test -f "$ARGUMENTS"), then read it. Save the path:PLAN_FILE="$ARGUMENTS"(used later for bidirectional linking). -
With text (
/plan-to-issues "Add caching layer"): If$ARGUMENTSis not a valid file path, use it as plan description. SetPLAN_FILE=""(no file to link back to). -
Without arguments (
/plan-to-issues): Readdocs/codingbuddy/context.mdand extract the most recent PLAN section's decisions and notes. SetPLAN_FILE=""(no file to link back to).
If no plan source is found, stop and ask the user to run PLAN first.
Step 2: Check GitHub Environment
REPO=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
gh label list --json name --jq '.[].name'
Search for existing issues with similar titles to prevent duplicates:
gh issue list --state open --search "<plan-title-keywords>" --json number,title --jq '.[] | "#\(.number) \(.title)"'
If duplicates found, inform the user and ask whether to continue or update existing issues.
Step 3: Decompose into Deployable Units
Extract work units from the plan. For each candidate unit, verify:
For each unit:
Can this be merged independently without breaking existing features?
├── YES → Keep as separate sub-issue
└── NO → Merge with related unit(s) into one sub-issue
Does this modify the same files as another unit?
├── YES → Consider merging or enforce ordering
└── NO → Safe for parallel work
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.
- 2d ago First seen · 356 lines · 57 tokens per session scan A 06ec20c60839
plan-to-issues is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 2,698 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-30.
Other skills, from other repositories
om-integration-builder
Build integration provider packages for the Open Mercato Integration Marketplace (payment, shipping, data-sync, webhook). Scaffolds the npm package, adapter, credentials, widget injection, webhook processing, health checks, i18n, tests. Triggers on "build integration", "add provider", "integrate with…
om-ds-guardian
Design System Guardian for Open Mercato. Use for frontend UI work, design-system compliance reviews, semantic token migration, hardcoded color or typography cleanup, DS-compliant page scaffolding, and common DS violations such as arbitrary text sizes, raw color classes, or missing shared states. Prefer this skill…
om-integration-tests
Run and create QA integration tests (Playwright TypeScript), including executing the full suite, converting optional markdown scenarios, and generating new tests from specs or feature descriptions. Defers all environment boot/reuse to the om-prepare-test-env skill and attaches to the shared descriptor it writes. Use…
om-auto-qa-scenarios
Generate a human QA report for a window of merged PRs (date floor, PR-number floor, or default last 7 days) and ship it as a docs-only PR against develop. Groups work into P0/P1/P2 testing routes with click paths, verification points, and risk callouts. Writes markdown + HTML under .ai/analysis/. Hands off to…
om-create-agents-md
Create or rewrite AGENTS.md files for Open Mercato packages and modules. Use this skill when adding a new package, creating a new module, or when an existing AGENTS.md needs to be created or refactored. Ensures prescriptive tone, the Always/Ask First/Never/Validation Commands boundary structure, MUST-style rules…
om-smart-test
Run only the tests affected by changed code. Use when the user says "run affected tests", "run smart tests", "test only what changed", "run tests for this PR", "run tests for my changes", "selective tests", or asks to run tests without running the full suite.