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 Mr-pixle/jira-mcp --skill onboard-projectgit clone --depth 1 https://github.com/Mr-pixle/jira-mcpWrote 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/mr-pixle/jira-mcp/onboard-project)<a href="https://agentmods.dev/skills/mr-pixle/jira-mcp/onboard-project"><img src="https://agentmods.dev/badge/skills/mr-pixle/jira-mcp/onboard-project/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/mr-pixle/jira-mcp/onboard-project"><img src="https://agentmods.dev/badge/skills/mr-pixle/jira-mcp/onboard-project.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.00096 | $0.01276 |
| Opus 5 | $0.00048 | $0.00638 |
| Sonnet 5 | $0.00019 | $0.00255 |
| Haiku 4.5 | $0.00010 | $0.00128 |
Grade A, and why
onboard-project 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Onboarding
Keywords
new project, unfamiliar project, how does this team work, project structure, who works on what, explain this project, get oriented, onboarding, workflow, پروژه جدید, ساختار پروژه, آشنایی با پروژه
Build an accurate picture of a Jira project before working in it — its configuration, its people, and the conventions that are not written down anywhere.
Entirely read-only.
Why this matters
Most failed Jira queries fail on vocabulary. A status called "In Review" on one board is "Code Review" on another; a project keyed OPS might be named "Platform Operations". Getting these right once, up front, saves a series of empty result sets later.
Workflow
Step 1 — The project itself
Project.get with detail="full" — name, key, lead, description, issue types.
If the user gave a name rather than a key, Project.list with name_contains finds it. Confirm before proceeding when more than one matches.
Step 2 — The vocabulary
This is the part that pays off later.
Statuses and types: Project.get_issue_types. Note that workflows differ per issue type — a Bug and a Story in the same project can have different statuses. Record the exact names; JQL is unforgiving about them.
Components: Project.get_components. These usually map to the system's architecture and are the most useful filter after project.
Versions: Project.get_versions. Shows the release cadence — a project with monthly versions works differently from one with two a year.
Custom fields: Field.list with custom_only=true. Look for the ones that carry meaning: Story Points, Sprint, Epic Link, Flagged, and any team-specific field.
Step 3 — The boards
Board.list with the project key.
For each board, Board.get_configuration gives:
- Columns and their statuses — the team's actual workflow, which often differs from the raw status list
- The estimation field — whether they estimate, and in what
- The filter — sometimes reveals that a board covers several projects, or only part of one
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 · 122 lines · 96 tokens per session scan A 3adc55fddaf7
onboard-project is a skill published in the GitHub repository Mr-pixle/jira-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,276 once invoked, about $0.0005 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
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.