Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add paulbaranowski/wild-horses/plugin install plan-keeperWrote 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/paulbaranowski/wild-horses/plan-jira)<a href="https://agentmods.dev/skills/paulbaranowski/wild-horses/plan-jira"><img src="https://agentmods.dev/badge/skills/paulbaranowski/wild-horses/plan-jira/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/paulbaranowski/wild-horses/plan-jira"><img src="https://agentmods.dev/badge/skills/paulbaranowski/wild-horses/plan-jira.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.00060 | $0.02463 |
| Opus 5 | $0.00030 | $0.01231 |
| Sonnet 5 | $0.00012 | $0.00493 |
| Haiku 4.5 | $0.00006 | $0.00246 |
Grade B, and why
plan-jira scanned grade B 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Don't** edit `.plankeeper.json` with `Edit` or `Write`. Use `jira config save` so atomic write + chmod 600 happen. How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-jira
Push a saved plan markdown file as a Jira ticket description. On first push, write the Jira Ticket id into the file's frontmatter so the same plan can be re-pushed (updates the existing ticket instead of creating a new one). Per-repo config — including the API token — lives at ~/plans/<repo>/.plankeeper.json (see ../../ticket-systems.md).
The bundled plan_keeper_cli.py does every mutation: config CRUD, metadata fetch, frontmatter read/write, and the actual Jira API calls. This skill's job is the user-facing orchestration: arg parsing, file selection, setup wizard prompts, and final confirmation.
Invocation
/plan-jira [last|file]
The mode arg is optional.
Procedure
1. Parse the user's args
Tokenize the invocation. Recognize last and file as the mode arg. Anything else is an error (unrecognized argument). The mode arg may be absent.
2. Resolve the repo and check Jira config
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/plan_keeper_cli.py" repo name
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/plan_keeper_cli.py" jira config get
The first returns <repo> (e.g., herds). The second exits 0 (Jira is configured — its section prints as JSON) or exits 3 (not configured). On exit 3, go to step 3 (setup). On exit 0, continue to step 4.
3. Inline setup wizard (only if Jira isn't configured)
This step is only reached when jira config get exited 3. Walk the user through it:
3.1 — Get the credentials
AskUserQuestion: "Paste your Jira API token" (free-text via the "Other" path). Also ask for site (e.g., herds.atlassian.net) and email separately.
3.2 — Validate the credentials
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/plan_keeper_cli.py" jira api viewer \
--api-key <K> --site <s> --email <e>
- On non-zero exit (codes 3 / 4 / 5): surface the stderr message to the user, re-ask. After 3 failures, abort the whole flow.
- On exit 0: stdout contains the authenticated identity as JSON.
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.
- 11d ago First seen · 221 lines · 60 tokens per session scan B 5a69d329e3ce
plan-jira is a skill published in the GitHub repository paulbaranowski/wild-horses (12 stars, last pushed 23d ago), licensed MIT. It adds 60 tokens to every session and 2,463 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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.