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 brain-bootstrap/claude-code-brain-bootstrap --skill ticketgit clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapWrote 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/brain-bootstrap/claude-code-brain-bootstrap/ticket)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/ticket"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/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/brain-bootstrap/claude-code-brain-bootstrap/ticket"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/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.00037 | $0.00370 |
| Opus 5.5 | $0.00015 | $0.00148 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
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 1mo 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
Ticket Skill
Create a well-structured ticket/issue description backed by evidence from the codebase.
Usage
/ticket Bug: login fails when email has uppercase letters
/ticket Feature: add pagination to the orders list endpoint
Protocol
1. Parse the Request
- Bug or Story?
- Which services/files are affected?
- Current vs expected behavior (for bugs)?
2. Research the Codebase
- Read relevant source files
- Collect evidence: file paths + line numbers
- Find root cause (for bugs) or integration points (for features)
3. Write the Ticket
Read claude/templates.md for the ticket template format.
For bugs, include:
- Steps to reproduce (exact commands or UI steps)
- Current behavior (with evidence)
- Expected behavior
- Root cause (file path + line number)
- Proposed fix (specific files to change)
For features, include:
- Problem statement / user story
- Acceptance criteria (testable, not vague)
- Technical approach (specific files/APIs to change)
- Out of scope (explicit boundaries)
4. Quality Rules
- Every claim must be backed by evidence (file path + line number)
- Acceptance criteria must be testable
- Proposed solution must reference exact files to change
- No vague statements like "improve performance" — be specific
5. Save and Report
Save to claude/tasks/ticket-<slug>.md where <slug> is a kebab-case summary.
Tell the user the exact file path.
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.
- 1mo ago First seen · 55 lines · 37 tokens per session scan A 0fbddf565188
ticket is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 370 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-09-03.
Other skills, from other repositories
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…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
maggy
Maggy is a local AI engineering command center. AI-prioritized inbox across issue trackers (GitHub Issues/Asana), one-click TDD execute with iCPG context enrichment, daily competitor intelligence briefing.