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 codecast-sh/codecast --skill cast-conflictsgit clone --depth 1 https://github.com/codecast-sh/codecastWrote 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/codecast-sh/codecast/cast-conflicts)<a href="https://agentmods.dev/skills/codecast-sh/codecast/cast-conflicts"><img src="https://agentmods.dev/badge/skills/codecast-sh/codecast/cast-conflicts/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/codecast-sh/codecast/cast-conflicts"><img src="https://agentmods.dev/badge/skills/codecast-sh/codecast/cast-conflicts.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.00059 | $0.00471 |
| Opus 5.5 | $0.00024 | $0.00188 |
| Sonnet 5.5 | $0.00012 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
cast-conflicts 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
Merge conflicts in shared files are the failure no fleet tool detects before it happens. This finds them while both sides can still adjust.
My file set
The argument, if given. Otherwise the files in git status --porcelain plus
any files named in cast task context --current. When the question is about
work you are about to spawn, use the files each brief will touch.
Their file sets
cast sessions --state working --json
cast sessions --state needs-input --json
cast links # this session's id, to exclude it
Keep sessions whose project_path is this repository or a worktree of it
(.codecast/worktrees/<name> and .claude/worktrees/<name> under the same
root count). For each:
cast diff <id> # "Files Changed" with +/- per file
cast state show <id> # what it says it is doing
Paths in cast diff are abbreviated from the left, so match on the path tail.
Report
No overlap is a one line answer. Otherwise a table: session (short id), what
it is doing, the overlapping files, its line counts, and when it last moved.
For each overlap read the relevant hunks with cast diff <id> --patch and say
whether the two changes can coexist, will conflict textually, or conflict in
meaning (same function, different intent).
Act
Tell the other session what you are about to change in the shared file with
cast send <id>; one message, concrete, no status narration. Then choose:
sequence the work, split the file ownership, or rebase onto their change when
it lands. When spawning workers, write the file ownership into each brief so
no two briefs claim one file.
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 · 50 lines · 59 tokens per session scan A 4a63a90a825a
cast-conflicts is a skill published in the GitHub repository codecast-sh/codecast (40 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 471 once invoked, about $0.0002 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-15.
Other skills, from other repositories
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
pn-github-vertical-slices
Break a plan or PRD into tracer-bullet vertical slices and create GitHub Issues via GitHub MCP (official github/github-mcp-server). Dependencies first (AFK/HITL). Use after pn-writing-plans or pn-create-prd when work must ship as Issues.
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.