Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/it235/multica-best-practicesnpx agentmods add skills/it235/multica-best-practices/multica-platform-jiraWrote 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/it235/multica-best-practices/multica-platform-jira)<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-platform-jira"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-platform-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/it235/multica-best-practices/multica-platform-jira"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-platform-jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Rogue Agent · line 12 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00000 | $0.00821 |
| Opus 5 | $0.00000 | $0.00411 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
multica-platform-jira 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform · JIRA (placeholder shell)
This is a platform-layer placeholder shell. The public multica-best-practices binds to no specific company's internal URLs or credentials. To onboard your own Issue system, only edit this skill's
config.yamlandscripts/; all upstream roles and orchestration skills stay untouched.
Purpose
Provide read + write capability for "Issue-tracking system" class platforms:
- Read: query Issues, parse Wiki links from descriptions, JQL / conditional search.
- Write: create Stories, transition states, schedule, append to description (write back Wiki links), notify.
Decoupled from multica-platform-confluence (Wiki); this skill only handles the Issue system, not Wiki page creation.
Files (suggested structure)
multica-platform-jira/
├── SKILL.md
├── config.yaml
├── .env.example
└── scripts/
├── credentials.sh
├── issue.sh
└── validate.sh
Read (pull Issue / locate upstream Wiki)
bash scripts/issue.sh get-issue <ISSUE-KEY>
bash scripts/issue.sh get-wiki-url <ISSUE-KEY> [text|json]
bash scripts/issue.sh search "<JQL>" [max_results]
Typical chain: get-issue reads acceptance criteria → get-wiki-url gets PRD pageId → multica-platform-confluence fetch-page pulls body.
Write (artifact / workflow write-back)
bash scripts/issue.sh create-story --project <PREFIX> --summary "..." ...
bash scripts/issue.sh get-transitions <ISSUE-KEY>
bash scripts/issue.sh transition <ISSUE-KEY> <state_name>
bash scripts/issue.sh schedule <ISSUE-KEY> <owner> <start> <end>
bash scripts/issue.sh append-description <ISSUE-KEY> "<wiki_link_block>"
bash scripts/issue.sh notify <ISSUE-KEY> <wiki_page_id>
Wiki description format
The markup syntax for the appended block depends on the target system (Jira Wiki / Markdown / plain text), implemented inside scripts/; characters needing escaping are handled per target-system rules.
Workflow: Wiki-blocked degradation (PRD)
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 · 79 lines · 0 tokens per session scan A 2ac254c89868
multica-platform-jira is a skill published in the GitHub repository it235/multica-best-practices (108 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 821 tokens. 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.