Borrowing it
Nothing to install: this file belongs to opensupplyhub/open-supply-hub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opensupplyhub/open-supply-hub/main/.agent/skills/plan-ticket/SKILL.mdgit clone --depth 1 https://github.com/opensupplyhub/open-supply-hubWrote 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/opensupplyhub/open-supply-hub/plan-ticket)<a href="https://agentmods.dev/skills/opensupplyhub/open-supply-hub/plan-ticket"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/plan-ticket/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/opensupplyhub/open-supply-hub/plan-ticket"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/plan-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 8 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00052 | $0.01078 |
| Opus 5 | $0.00026 | $0.00539 |
| Sonnet 5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
plan-ticket 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 10d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning an OS Hub Ticket
The job: read the ticket, do real research, write a quality plan to a markdown file. No code. No branches. No commits. Just the plan.
Step 1 — Confirm the ticket
If the user did not name a ticket, ask:
Which ticket should I plan? Reply with the OSDEV key (e.g., OSDEV-2316).
Step 2 — Read the ticket
Fetch from Jira via the Atlassian MCP. The OS Hub Atlassian site is opensupplyhub.atlassian.net — use this to identify the workspace when calling the MCP.
Extract: summary, description, acceptance criteria, labels.
Step 3 — Name the complexity
State the complexity level and the reason in one sentence. The user decides what to do with that information.
- RED — touches dedupe pipeline, ECS/Terraform, or core DB schema
- YELLOW — new Django model, full-stack change, or touches search
- GREEN — text changes, new field in an existing API, or new UI component
Step 4 — Research
Pull from every source available. The goal is a quality plan, not just any plan.
- The codebase — find similar features, read them as templates. If the OS Hub Codebase Expert sub-agent is available, delegate this; otherwise read directly.
- Confluence — search the OS Hub Development Home space for the feature, related specs, or prior decisions.
- GitHub —
git log --oneline -20andgh pr list --state merged --limit 15 --json title,number,filesfor recent similar PRs. - AGENTS.md and the
.agent/skills/resources — apply existing conventions, patterns, known gotchas. - Session context and memory — anything shared earlier or auto-loaded.
- External connectors (optional) — ask once: "Do you have Granola, Google Drive, Monday, HubSpot, or other MCP connectors with context that might help on this ticket?" If yes, pull from them. If no or unsure, skip and continue.
If you can't find something, say so. Don't guess.
Step 5 — Write the plan to a markdown file
Save to ~/.claude/plans/OSDEV-####.md (create the directory if needed).
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.
- 10d ago First seen · 87 lines · 52 tokens per session scan A f6139cfcdda1
plan-ticket is a skill published in the GitHub repository opensupplyhub/open-supply-hub (20 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,078 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.