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 commands/ruvnet/ruv-fann/conflictsgit clone --depth 1 https://github.com/ruvnet/ruv-FANNWrote 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/commands/ruvnet/ruv-fann/conflicts)<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/conflicts"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/conflicts.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00760 |
| Opus 5 | $0.00000 | $0.00380 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
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 5d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/github conflicts
Detects and displays potential conflicts between swarms working on the same codebase.
Usage
/github conflicts [options]
Options
--scope <type>- Check specific conflict types (files, tasks, areas)--resolve- Show resolution suggestions
Examples
/github conflicts
/github conflicts --scope files
/github conflicts --resolve
Conflict Types
- File Conflicts - Multiple swarms editing same files
- Task Dependencies - Blocked or related tasks
- Area Overlap - Same component/module work
- Resource Competition - Same test suites, benchmarks
Implementation
Uses GitHub MCP to:
- Analyze current swarm activities
- Check PR files being modified
- Compare task descriptions
- Identify overlapping work
Example Output
Basic Conflict Check
🔍 Conflict Analysis
⚠️ 2 Potential Conflicts Detected:
1. FILE CONFLICT - High Priority
Swarms: swarm-alpha-123, swarm-beta-456
File: src/neural-agent.js
swarm-alpha-123: Optimizing memory usage
swarm-beta-456: Fixing pattern storage
Risk: Merge conflicts likely
2. DEPENDENCY CONFLICT - Medium Priority
Swarms: swarm-gamma-789, swarm-delta-012
swarm-gamma-789: Working on #52 (needs #51)
swarm-delta-012: Working on #51 (blocking)
Risk: Gamma blocked until Delta completes
✅ No conflicts: 3 other active swarms
With Resolution Suggestions
🔍 Conflict Analysis with Resolutions
⚠️ FILE CONFLICT: src/neural-agent.js
Affected Swarms:
- swarm-alpha-123 (Issue #45)
- swarm-beta-456 (Issue #52)
📋 Suggested Resolution:
1. Comment on both issues about overlap
2. Suggested split:
- Alpha: Focus on memory optimization methods
- Beta: Focus on storage implementation
3. Create shared branch for coordination
4. Schedule sync point in 2 hours
💬 Sample Coordination Message:
"Hi @swarm-beta-456, I'm working on memory optimization
in neural-agent.js. I'll focus on the cleanup methods
(lines 100-200). Can you work on storage (lines 300-400)?
Let's sync before merging."
[Copy message to clipboard]
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.
- 5d ago First seen · 130 lines · 0 tokens per session scan A c612bb784892
conflicts is a command published in the GitHub repository ruvnet/ruv-FANN (378 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 760 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.