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/XAIHT/Tlamatininpx agentmods add skills/xaiht/tlamatini/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/xaiht/tlamatini/jira)<a href="https://agentmods.dev/skills/xaiht/tlamatini/jira"><img src="https://agentmods.dev/badge/skills/xaiht/tlamatini/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/xaiht/tlamatini/jira"><img src="https://agentmods.dev/badge/skills/xaiht/tlamatini/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.00019 | $0.00672 |
| Opus 5.5 | $0.00008 | $0.00269 |
| Sonnet 5.5 | $0.00004 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
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 3d 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.
What it actually says
Jira skill
Current release: v1.91.0. Dated records below retain their original evidence dates.
HEADLESS IS FORBIDDEN. VISIBLE FOREGROUND EXECUTION ONLY. Every command, automated test, diagnostic, script, build, agent and browser must run in a visible foreground window on Angela's real desktop. Use forked CMD/PowerShell windows,
execute_forked_window: true, andheadless: false. Monitor live; if visibility cannot be confirmed, do not run. Read the mandatory execution policy.
Use the Jira REST API v3 for issues / comments / transitions.
Setup
JIRA_BASE_URL (e.g. https://your-domain.atlassian.net),
JIRA_EMAIL and JIRA_API_TOKEN must be in env.
Procedure
search→POST /rest/api/3/searchwith JQL in payload.get→GET /rest/api/3/issue/{key}.create→POST /rest/api/3/issuewith{ fields: {...} }.comment→POST /rest/api/3/issue/{key}/comment.transition→POST /rest/api/3/issue/{key}/transitions.
Use Basic Auth: base64(JIRA_EMAIL:JIRA_API_TOKEN).
Return the parsed JSON.
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.
- 3d ago Changed bd5955fe7092
- 4d ago Changed 5bb5b120b455
- 6d ago Changed 559be59c68fa
- 7d ago Changed 001736c74c0f
- 9d ago Changed · +3 lines 9d4bf1251597
- 1mo ago Changed · +2 lines f42e58945f36
- 1mo ago First seen · 61 lines · 19 tokens per session scan A 651006725ab2
jira is a skill published in the GitHub repository XAIHT/Tlamatini (15 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 672 once invoked, about $0.0001 per session on Opus 5.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
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
sn-team-harness
Use when a user asks what SenseNova Team Harness is, wants an introduction or overview, is getting started, or is deciding whether it fits — a self-hosted workspace where people and local AI agents collaborate on conversations, projects, work items, and artifacts. Covers its core concepts (Workspace, Project…
feature-request
Conversational workflow for gathering user feedback and filing GitHub Issues on the Kiro Crew repository. Load when the user clicks "Request a Feature", wants to report a bug, or suggest an improvement.
goal-loop
Bootstrap a goal-driven self-improving AutoNudge loop from a goal plus an anchor directory, then run the board autonomously until the Definition of Done is met.