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/ruvnet/sublinear-time-solverWrote 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/sublinear-time-solver/maintenance)<a href="https://agentmods.dev/commands/ruvnet/sublinear-time-solver/maintenance"><img src="https://agentmods.dev/badge/commands/ruvnet/sublinear-time-solver/maintenance/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/commands/ruvnet/sublinear-time-solver/maintenance"><img src="https://agentmods.dev/badge/commands/ruvnet/sublinear-time-solver/maintenance.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.00000 | $0.00561 |
| Opus 5.5 | $0.00000 | $0.00224 |
| Sonnet 5.5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
maintenance 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.
This is a copy
100% identical to maintenance — 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintenance Swarm Strategy
Purpose
System maintenance and updates through coordinated agents.
Activation
Using MCP Tools
// Initialize maintenance swarm
mcp__claude-flow__swarm_init({
"topology": "star",
"maxAgents": 5,
"strategy": "sequential"
})
// Orchestrate maintenance task
mcp__claude-flow__task_orchestrate({
"task": "update dependencies",
"strategy": "sequential",
"priority": "medium",
"dependencies": ["backup", "test", "update", "verify"]
})
Using CLI (Fallback)
npx claude-flow swarm "update dependencies" --strategy maintenance
Agent Roles
Agent Spawning with MCP
// Spawn maintenance agents
mcp__claude-flow__agent_spawn({
"type": "analyst",
"name": "Dependency Analyzer",
"capabilities": ["dependency-analysis", "version-management"]
})
mcp__claude-flow__agent_spawn({
"type": "monitor",
"name": "Security Scanner",
"capabilities": ["security", "vulnerability-scan"]
})
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "Test Runner",
"capabilities": ["testing", "validation"]
})
mcp__claude-flow__agent_spawn({
"type": "documenter",
"name": "Documentation Updater",
"capabilities": ["documentation", "changelog"]
})
Safety Features
Backup and Recovery
// Create system backup
mcp__claude-flow__backup_create({
"components": ["code", "config", "dependencies"],
"destination": "./backups/maintenance-" + Date.now()
})
// Create state snapshot
mcp__claude-flow__state_snapshot({
"name": "pre-maintenance-" + Date.now()
})
// Enable fault tolerance
mcp__claude-flow__daa_fault_tolerance({
"agentId": "all",
"strategy": "checkpoint-recovery"
})
Security Scanning
// Run security scan
mcp__claude-flow__security_scan({
"target": "./",
"depth": "comprehensive"
})
Monitoring
// Health check before/after
mcp__claude-flow__health_check({
"components": ["dependencies", "tests", "build"]
})
// Monitor maintenance progress
mcp__claude-flow__swarm_monitor({
"swarmId": "maintenance-swarm",
"interval": 3000
})
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 · 103 lines · 0 tokens per session scan A 394a52b48772
maintenance is a command published in the GitHub repository ruvnet/sublinear-time-solver (91 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 561 tokens. A static security scan graded it A with 0 findings. It is 100% identical to maintenance, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
kshana-trust-telemetry
Render a GNSS trust stream or a receiver-trust result as Prometheus text, CEF or LEEF syslog lines or an OTLP payload via the kshana-mcp server.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
atrs
Generate Algorithmic Transparency Recording Standard (ATRS) record for AI/algorithmic tools.
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.