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/schedulesgit 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.00381 |
| Opus 5 | $0.00000 | $0.00191 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
schedules 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 -s "http://backend:8000/api/ops/schedules" \ What it actually says
Schedule Overview
Quick overview of all schedules across the platform.
Instructions
- Get schedule summary using the API:
curl -s "http://backend:8000/api/ops/schedules" \
-H "Authorization: Bearer $TRINITY_MCP_API_KEY" | jq '.summary'
- Generate a brief report:
## Schedule Overview
Generated: {timestamp}
- Total Schedules: {total}
- Enabled: {enabled}
- Disabled: {disabled}
- Agents with Schedules: {agents_with_schedules}
For detailed information, use:
- `/ops/schedules/list` - Full schedule listing
- `/ops/schedules/pause` - Pause schedules
- `/ops/schedules/resume` - Resume schedules
Related Commands
| Command | Purpose |
|---|---|
/ops/schedules/list |
Detailed schedule listing with execution history |
/ops/schedules/pause [agent] |
Pause all or agent-specific schedules |
/ops/schedules/resume [agent] |
Resume paused schedules |
/ops/executions/list |
View recent task executions |
/ops/executions/status <id> |
Get details of specific execution |
Quick Actions
Check if any schedules are failing:
curl -s "http://backend:8000/api/ops/schedules" \
-H "Authorization: Bearer $TRINITY_MCP_API_KEY" | \
jq '.schedules[] | select(.last_execution.status == "failed")'
Emergency pause all:
curl -X POST "http://backend:8000/api/ops/schedules/pause" \
-H "Authorization: Bearer $TRINITY_MCP_API_KEY"
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 · 55 lines · 0 tokens per session scan A 438dffbcf6b6
schedules 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 381 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.