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 skullninja/coco-workflow --skill hotfixgit clone --depth 1 https://github.com/skullninja/coco-workflowWrote 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/skullninja/coco-workflow/hotfix)<a href="https://agentmods.dev/skills/skullninja/coco-workflow/hotfix"><img src="https://agentmods.dev/badge/skills/skullninja/coco-workflow/hotfix/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/skullninja/coco-workflow/hotfix"><img src="https://agentmods.dev/badge/skills/skullninja/coco-workflow/hotfix.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.00036 | $0.01425 |
| Opus 5.5 | $0.00014 | $0.00570 |
| Sonnet 5.5 | $0.00007 | $0.00285 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
hotfix 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coco Hotfix Skill
Lightweight workflow for single-issue fixes and small changes that don't warrant full epic tracking.
When to Use
- Bug fixes that affect a single area
- Small enhancements (< 1 day of work)
- Quick changes where dependency tracking isn't needed
- Any work that maps to a single issue tracker entry
For multi-session features with dependencies, use the execute skill instead.
Workflow
1. Setup
Read .coco/config.yaml for issue tracker configuration.
If $ARGUMENTS contains an issue key/ID, load it. Otherwise, create a new issue:
If "linear":
Use: mcp__plugin_linear_linear__create_issue
Parameters:
title: "{fix description}"
team: {from config issue_tracker.linear.team}
labels: {from config issue_tracker.linear.labels}
state: "In Progress"
If "github":
gh issue create --title "{fix description}" --label "{comma-separated labels from issue_tracker.github.labels in config}"
If github.use_projects is true: check .coco/state/gh-projects.json for an active feature project. If one exists, add the issue to it and set status to "In Progress":
gh project item-add {project_number} --owner {github.owner} --url {issue_url}
gh project item-edit --project-id {project_id} --id {item_id} --field-id {status_field_id} --single-select-option-id {status_options["In Progress"]}
If "none": Skip issue creation.
2. Create Branch
git checkout -b fix/{short-name}
3. Implement Fix
- Understand the issue (read related code, reproduce if bug)
- For a bug: reproduce it in a failing test first. A bug that shipped once is proof the failure mode is real and undefended -- that is the highest-value test there is, and it is the one case where a test is always worth writing
- For a non-bug change (config, docs, a small refactor), write a test only if it defends a failure mode nothing else covers. Do not add a test purely to accompany the diff
- Implement the fix
- Run test suite to verify no regressions
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 · 181 lines · 36 tokens per session scan A eb5c56d3c038
hotfix is a skill published in the GitHub repository skullninja/coco-workflow (8 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 1,425 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-31.
Other skills, from other repositories
ccc-triage
Triage a GitHub repo's open issues and PRs with the gh CLI: flag stale, unlabeled and CI-failing items, propose labels and next actions, apply labels one confirmed item at a time, or summarize the backlog. Use when a maintainer asks to triage issues or PRs, label the backlog, or wants a digest.
ccc-tasks
Track work in one markdown file, tasks/todo.md, with checkboxes, P0-P3 priorities and status marks; no database, service or sync. Use when the user asks for a todo list, wants to track personal or side-session tasks, or types $ccc-tasks.
g-update
Fix G-Forge-managed files via Step 0 staleness preflight (stops with zero writes if cache lags GitHub, directs to /plugins first), then realigns CLAUDE.md Rules, agents, architecture rules, hooks, and native pre-commit gate. Safe — G-Forge markers only.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.