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 jxoesneon/Ciel --skill jira-integrationgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/jira-integration)<a href="https://agentmods.dev/skills/jxoesneon/ciel/jira-integration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/jira-integration/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/jxoesneon/ciel/jira-integration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/jira-integration.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.00021 | $0.00501 |
| Opus 5 | $0.00010 | $0.00251 |
| Sonnet 5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
jira-integration scanned grade A 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **REST Fallback**: Uses `curl` with `JIRA_API_TOKEN` for environments where MCP is unavailable. What it actually says
CIEL ADAPTATION: Jira Integration (Issue Tracking)
This skill formalizes how CIEL interacts with Jira for requirements gathering, status updates, and development tracking. It prioritizes the mcp-atlassian server for tool-based interaction.
Core Interaction Modes
- MCP (Preferred): Uses
jira_get_issue,jira_search, andjira_transition_issuefor structured, authenticated operations. - REST Fallback: Uses
curlwithJIRA_API_TOKENfor environments where MCP is unavailable.
Requirements Extraction Protocol
When reading a ticket, the Orchestrator MUST extract:
- Testable AC: Specific, binary conditions for success.
- Functional Scope: What is being changed vs. what is out of scope.
- Integration Points: Affected services, APIs, or database schemas.
- Edge Cases: Negative tests and boundary conditions defined in the ticket.
TICKET UPDATE Lifecycle
- START: Transition to
In Progressand comment with the implementation branch name. - VERIFY: Comment with a summary of test results and coverage after the
verification-looppasses. - FINISH: Transition to
DoneorIn Reviewand link the final PR/Commit.
Anti-Patterns
- Secret Leaking: Hardcoding API tokens in scripts or session notes.
- Vague Updates: Commenting "Working on it" without providing a branch or specific task context.
- Status Drift: Implementing features that contradict the ticket's Acceptance Criteria without clarifying first.
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.
- 8d ago First seen · 52 lines · 21 tokens per session scan A f24324aabf72
jira-integration is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 21 tokens to every session and 501 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
factory-handoff
Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
feature-flow
Cria o diretório canônico da task (docs/todo/NNN-slug/), a branch e o scaffolding inicial. Use para "criar feature", "iniciar tarefa" ou "abrir task".
task-tracker
Escaneia docs/todo/ reportando o Status de cada task e arquiva em docs/done/ somente as entregues. Use para "verificar tasks", "o que está pendente" ou "arquivar concluídas".
autonomous-project-manager
This is the 'Master Blueprint' for long-running autonomous tasks. Modeled after the 'Ralph Wiggum' pattern, it forces the agent to maintain persistent memory and state files for an entire portfolio of projects.
feature-retirement-comms-planner
Identifies users dependent on a feature being removed. Drafts a timeline of 3 emails: 'Heads up', 'Alternative Workflows', and 'Final Reminder'.