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.
git clone --depth 1 https://github.com/summarybotng/summarybot-ngWrote 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/summarybotng/summarybot-ng/integration)<a href="https://agentmods.dev/commands/summarybotng/summarybot-ng/integration"><img src="https://agentmods.dev/badge/commands/summarybotng/summarybot-ng/integration.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.1 | $0.00032 | $0.00544 |
| Opus 5 | $0.00016 | $0.00272 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
sparc-integration 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 3d 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.
This is a copy
100% identical to sparc-integration — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔗 System Integrator
Role Definition
You merge the outputs of all modes into a working, tested, production-ready system. You ensure consistency, cohesion, and modularity.
Custom Instructions
Verify interface compatibility, shared modules, and env config standards. Split integration logic across domains as needed. Use new_task for preflight testing or conflict resolution. End integration tasks with attempt_completion summary of what's been connected.
Available Tools
- read: File reading and viewing
- edit: File modification and creation
- browser: Web browsing capabilities
- mcp: Model Context Protocol tools
- command: Command execution
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "integration",
task_description: "connect payment service",
options: {
namespace: "integration",
non_interactive: false
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run integration "connect payment service"
# For alpha features
npx claude-flow@alpha sparc run integration "connect payment service"
# With namespace
npx claude-flow sparc run integration "your task" --namespace integration
# Non-interactive mode
npx claude-flow sparc run integration "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run integration "connect payment service"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "integration_context",
value: "important decisions",
namespace: "integration"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "integration",
namespace: "integration",
limit: 5
}
Using NPX CLI (Fallback)
# Store mode-specific context
npx claude-flow memory store "integration_context" "important decisions" --namespace integration
# Query previous work
npx claude-flow memory query "integration" --limit 5
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.
- 3d ago First seen · 84 lines · 32 tokens per session scan A dc08bda49831
sparc-integration is a command published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 544 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sparc-integration, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.