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/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/sprint-status)<a href="https://agentmods.dev/commands/cveralyon/axel-setup/sprint-status"><img src="https://agentmods.dev/badge/commands/cveralyon/axel-setup/sprint-status.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.00000 | $0.06751 |
| Opus 5 | $0.00000 | $0.03376 |
| Sonnet 5 | $0.00000 | $0.01350 |
| Haiku 4.5 | $0.00000 | $0.00675 |
Grade A, and why
sprint-status 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 6d 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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Status — Consolidate everything into Linear + generate review outputs
The heaviest command. Ingests Linear + Git across all configured repos + Slack (channels + DMs) — plus optional Notion and Intercom if your team uses them — deduplicates, and writes the consolidated state back into Linear (creating missing issues, updating statuses, reassigning based on git authorship). Then produces three separate outputs.
Linear is the single source of truth. Git, Slack, Notion, and Intercom are inputs that feed Linear. When Notion is configured, it is a historical view only — this command NEVER creates cards in Notion, only reads from it and (optionally) updates state of existing cards that are desynced.
Configuration (edit this section for your team)
Before using this skill, edit the YAML block below with your team's repos, channels, Linear setup, and integrations. Sections marked [OPTIONAL] can be deleted if your team does not use that system. Replace every Cxxxxxxx / Uxxxxxxx / xxxxx-xxxx placeholder with real IDs from your workspace.
# --- Linear workspace ---
linear:
team_name: "YourTeam"
team_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
team_key: "TEAM" # Used as issue prefix (e.g. TEAM-123)
primary_user_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
primary_user_email: "[email protected]"
# --- Team member mapping (git email ≠ Linear email is common) ---
team_members:
- git_email: "[email protected]"
name: "You"
linear_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
- git_email: "[email protected]"
name: "Teammate"
linear_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
- git_email: "[email protected]"
name: "PM"
linear_id: null # Never in Linear — never assign
# --- Git repos to scan ---
git_repos:
- ~/your-org/api-repo
- ~/your-org/frontend-repo
# --- Slack channels ---
slack_channels:
- { name: "#clients", id: "Cxxxxxxx" }
- { name: "#tech-guild", id: "Cxxxxxxx" }
- { name: "#incidents", id: "Cxxxxxxx" }
# --- Slack DMs (privacy gate applies) ---
slack_dms:
- { name: "PM/CEO", id: "Uxxxxxxx" }
- { name: "CS Lead", id: "Uxxxxxxx" }
# --- Optional integrations ---
integrations:
notion: false # [OPTIONAL] Sprints/Backlog DBs
intercom: false # [OPTIONAL] Client conversations
notion: # Only read if integrations.notion = true
sprints_db_id: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
backlog_db_id: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
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.
- 6d ago First seen · 487 lines · 0 tokens per session scan A dd71aa1828ec
sprint-status is a command published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,751 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-31.
Other commands, from other repositories
orc
Parallel multi-agent orchestration for complex features.
parallel-task
Execute bulk modifications across codebase with parallel agents and safety guarantees.
analytics-review
Review analytics and recent commits, then create tasks.
fix-issues
Pick up one approved task, implement the fix, and close it.
add-issue
Help the user create a task for a manually identified item (bug, feature, or improvement).
update-config
Update Dark Flow project settings: language and/or main branch.