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 flaio-ai/flaio --skill ticketgit clone --depth 1 https://github.com/flaio-ai/flaioWrote 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/flaio-ai/flaio/ticket)<a href="https://agentmods.dev/skills/flaio-ai/flaio/ticket"><img src="https://agentmods.dev/badge/skills/flaio-ai/flaio/ticket/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/flaio-ai/flaio/ticket"><img src="https://agentmods.dev/badge/skills/flaio-ai/flaio/ticket.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.00031 | $0.00486 |
| Opus 5.5 | $0.00012 | $0.00194 |
| Sonnet 5.5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
ticket 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 yesterday.
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
Load Flaio ticket $ARGUMENTS into this session.
- Call the
get_ticket_contexttool from theflaioMCP server.- If it succeeds and
ticketIdis$ARGUMENTS, use that context. - If the tool is unavailable, errors with "No Flaio ticket is bound", or returns a different ticket, continue with step 2.
- If it succeeds and
- Look for the ticket workspace in the current repository:
.flaio/ticket/brief.md,plan.md,decisions.md,progress.md,questions.mdandstate.json. Read the files that exist. Ifstate.jsonnames a differentticketId, treat the workspace as belonging to another ticket and don't use it. - If there's no usable workspace, run
flaio tickets get $ARGUMENTS --jsonwith the Bash tool to fetch the ticket (requiresflaio login). Then create the workspace so the Flaio tools work in this session:- write the ticket title, description, acceptance criteria and any plan to
.flaio/ticket/brief.md; - write
{"ticketId": "<the ticket id>"}to.flaio/ticket/state.json; - make sure
.flaio/is listed in the repository's.git/info/exclude(for a linked worktree, usegit rev-parse --git-common-dirto find it), so the workspace is never committed.
- write the ticket title, description, acceptance criteria and any plan to
- Summarize for the user in a few lines: what the ticket asks for, the current plan (if any), the last handoff note in
progress.md(if any), and open questions. Then ask how they want to proceed. Don't start changing code yet.
While working on the ticket, use the Flaio tools: submit_plan for plans, ask_question when blocked on a human, record_decision for notable choices, report_progress per step, and complete_phase to finish. Before ending the session, run /flaio:handoff.
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.
- yesterday First seen · 20 lines · 31 tokens per session scan A 04dadf0033d4
ticket is a skill published in the GitHub repository flaio-ai/flaio (2 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 486 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-11-13.
ticket compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ticketflaio-ai/flaio | Skill | 2 | 2d ago | MIT | A | 31 | Claude Code |
| imagegenopenai/codex | Skill | 135k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 80k | 7d ago | MIT | A | 200 | Claude Code, Codex |
| next-cache-components-adoptionvercel/next.js | Skill | 144k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |