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/abilityai/trinity/pausegit clone --depth 1 https://github.com/Abilityai/trinityWhat 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.00398 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
pause scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "http://backend:8000/api/ops/schedules/pause?agent_name={agent-name}" \ What it actually says
Pause Schedules
Pause one or more schedules to temporarily stop automated executions.
Arguments
<agent-name>(optional) - Only pause schedules for this agentall- Pause all schedules across all agents
Instructions
Pause All Schedules for an Agent
curl -X POST "http://backend:8000/api/ops/schedules/pause?agent_name={agent-name}" \
-H "Authorization: Bearer $TRINITY_MCP_API_KEY"
Pause All Schedules (Platform-wide)
curl -X POST "http://backend:8000/api/ops/schedules/pause" \
-H "Authorization: Bearer $TRINITY_MCP_API_KEY"
Response
The API returns:
{
"success": true,
"message": "Paused X schedule(s)",
"paused_count": X,
"agent_filter": "agent-name or null"
}
Report Format
## Schedules Paused
Timestamp: {timestamp}
Action: Paused {paused_count} schedule(s)
Scope: {agent_name or "All agents"}
### What This Means
- Paused schedules will NOT execute automatically
- Schedules remain configured and can be resumed
- Manual executions still possible via UI/API
### To Resume
Use `/ops/schedules/resume` or `/ops/schedules/resume {agent-name}`
Use Cases
- Maintenance Window: Pause all schedules before system updates
- Cost Control: Stop automated tasks during cost review
- Debugging: Pause specific agent's schedules while investigating issues
- Incident Response: Quick way to halt all automation
Caution
- This is an admin operation
- Does not affect currently running tasks
- Use
/ops/schedules/listto verify which schedules are affected
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.
- 2d ago First seen · 68 lines · 0 tokens per session scan A 4070a35d66e7
pause is a command published in the GitHub repository Abilityai/trinity (496 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 398 tokens. A static security scan graded it A with 1 finding (makes network calls). 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.