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 agentmods add skills/codoop/codoop-flow/codoop-ticketnpx skills add Codoop/codoop-flow --skill codoop-ticketgit clone --depth 1 https://github.com/Codoop/codoop-flowWhat 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 | $0.00066 | $0.04889 |
| Opus 5 | $0.00033 | $0.02445 |
| Sonnet 5 | $0.00013 | $0.00978 |
| Haiku 4.5 | $0.00007 | $0.00489 |
Grade A, and why
codoop-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.
How it starts
The opening of the file, as written. The whole thing — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codoop-Ticket — Ticket Design Orchestration
Help users systematically design work tickets in-session through three stages: requirements, technical specs, and task breakdown.
Project Paths
Read [project_paths] from codoop_flow.toml. If it is missing, run the
sibling codoop-init skill first. Values are the repository's real directories
and may use custom names. Generate implementation tasks only for configured
project types; describe unlisted systems only as external contracts.
Scope Boundary
This skill ends after an explicitly approved ticket is validated, committed, and
promoted to pending/. Do not implement, run, verify, review, or ship the
ticket; do not invoke codoop-execute or otherwise consume the pending queue.
Those are Phase 3 responsibilities and require a separate user request.
What is a Ticket?
A ticket is a complete design document package for one feature module:
| File | Purpose | Author |
|---|---|---|
module_prd.md |
Business requirements (pure business language, no tech) | PM agent |
spec.md |
Technical specification (APIs, DB, implementation details) | Architect agent |
preview.html |
Static, reviewable preview of a user-visible feature | Ticket agent, when required |
plan.md |
Implementation plan (steps) | Auto-inferred |
todo.md |
Atomic task list (≤100 lines code/task) | Auto-inferred |
metadata.json |
Ticket metadata (modules, execution settings) | Auto-inferred |
The table above shows a feature ticket. A fix ticket is lighter — see "Ticket Types" below.
Ticket Types
Every ticket has a ticket_type (stored in metadata.json, default feature):
| Type | For | Required docs | Skips |
|---|---|---|---|
feature |
New capability from a business need | module_prd.md + spec.md |
— |
fix |
Repairing an existing bug/defect | bug_report.md |
PRD + Spec stages |
plan.md + todo.md are recommended (not blocking) for both types.
Inferring the type — decide automatically. After the startup grilling
confirms shared understanding, infer the type
from the user's description (signals such as "fix", "bug", "error", or
"regression", including their equivalents in the user's language → fix;
otherwise feature) and scaffold. Do not ask the
user to confirm the type. If later context shows the type is wrong, change it
and regenerate the affected ticket documents.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 475 lines · 66 tokens per session scan A 907d17149285
codoop-ticket is a skill published in the GitHub repository Codoop/codoop-flow (5 stars, last pushed 8d ago), licensed MIT. It adds 66 tokens to every session and 4,889 once invoked, about $0.0003 per session on Opus 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-31.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
chatbot
Use when a support or sales bot on a live website must behave: persona/system prompt, grounding so it cannot invent prices or policy, jailbreak and injection defense, the human handoff, launch metrics and kill switch. NOT the agent loop or RAG index under it (that is building-agents), NOT a human answering one ticket…
agent-safety
Use when bounding an LLM agent that already runs — scoping its task domain, gating tools to least privilege, defending against prompt injection in untrusted web/email/RAG text, requiring human approval on irreversible actions, capping runtime and cost, or triaging what it already did. NOT building the loop, tools, or…
antidote
Stop AI agents from patching symptoms. Use this skill when coding, reviewing, refactoring, auditing, committing fixes, or adding guards, validation, workarounds, or 20+ lines without deleting code.
anti-slop-design
Category-aware design skill that builds distinctive, production-grade UIs. Brand-vs-product register, color strategy commitment, scene-based theme choice, palettes, font pairings, UX patterns, shadcn/token integration, empty-error-loading copy, secondary slop signals, multimodal design parity from mocks, and a…
3d-web-experiences
Build distinctive, performant, production-grade 3D on the web with Three.js, React Three Fiber, and WebGL. Use when the user asks to "build a 3D scene", "add a 3D hero/landing", "make a product viewer/configurator", mentions three.js / react-three-fiber / r3f / drei / webgl / shaders, or asks to make an existing 3D…