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 skills add Proxy2021/Enso --skill sprint_resultsgit clone --depth 1 https://github.com/Proxy2021/EnsoWrote 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/skills/proxy2021/enso/sprint_results)<a href="https://agentmods.dev/skills/proxy2021/enso/sprint_results"><img src="https://agentmods.dev/badge/skills/proxy2021/enso/sprint_results/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/skills/proxy2021/enso/sprint_results"><img src="https://agentmods.dev/badge/skills/proxy2021/enso/sprint_results.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.00047 | $0.00536 |
| Opus 5.5 | $0.00019 | $0.00214 |
| Sonnet 5.5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
sprint_results 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Results Dashboard — interactive view of focus area sprint deliverables with one-click actions, progress tracking, and shareable summaries. Shows deliverable cards, recommended first action, next steps, and focus area cycle progress.
Tool Reference
enso_sprint_results_load (primary)
Load sprint results for a focus area. Shows deliverable cards, recommended first action, next steps, and cycle progress. If no focusId is given, loads results for the most recently completed sprint. Use when the user says: 'show sprint results', 'sprint dashboard', 'what did the sprint produce', 'show deliverables', 'focus area results'.
Parameters:
focusId(string): Focus area ID to load results for. If omitted, loads the most recently completed sprint.
enso_sprint_results_launch
Launch or open a specific sprint deliverable. For apps, triggers a run. For articles/ideas/synthesis, opens the entity content. Use when the user clicks an action button on a deliverable card.
Parameters:
entityId(string): The Cortex entity ID of the deliverableentityType(string): Type: app, article, idea, or synthesisfocusId(string): Focus area ID for context
enso_sprint_results_next_cycle
Start the next evolution cycle for a focus area. Triggers a new Evaluate phase. Use when the user clicks 'Start Next Cycle'.
Parameters:
focusId(string): Focus area ID to start the next cycle for
enso_sprint_results_share
Generate a shareable text summary of sprint results. Produces a formatted summary suitable for sharing via email, chat, or notes. Use when the user clicks 'Share Results'.
Parameters:
focusId(string): Focus area IDformat(string): Output format: 'text' or 'markdown' (default: 'markdown')
enso_sprint_results_mark_status
Mark a deliverable's status as viewed or acted-on. Tracks engagement with sprint deliverables. Use when the user interacts with a deliverable.
Parameters:
focusId(string): Focus area IDentityId(string): The entity ID of the deliverablestatus(string): New status: 'viewed' or 'acted_on'
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- app.json 19 KB
- executors/activate.js 11 KB runs code
- executors/feedback.js 7.0 KB runs code
- executors/launch.js 15 KB runs code
- executors/load.js 9.7 KB runs code
- executors/mark_status.js 1.8 KB runs code
- executors/next_cycle.js 2.3 KB runs code
- executors/progress.js 8.6 KB runs code
- executors/share.js 4.0 KB runs code
- executors/value_map.js 4.4 KB runs code
- lib/deliverable-classifier.cjs 22 KB runs code
- lib/feedback-aggregator.cjs 5.9 KB runs code
- template.jsx 55 KB
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 · 49 lines · 47 tokens per session scan A 0bdede7458a2
sprint_results is a skill published in the GitHub repository Proxy2021/Enso (6 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 536 once invoked, about $0.0002 per session on Opus 5.5. 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 skills, from other repositories
run-github-project
Use when asked to set up, review, or operate a repository's GitHub Project workflow, including ready claims, role-labelled human work, unknown remote mutation outcomes, Todo triage, epics, checkpoints, next-issue execution, or an authorized drain.
deliver-spec
Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.
cross-squad
Coordinating work across multiple Squad instances.
release-manager
Automated release management skill for uiautomator2-mcp-server. Evaluates codebase status, runs checks, updates documentation, and manages the complete release workflow.
implement-issue
Use when asked to review, fix, implement, resolve, or work through a specific GitHub, GitLab, Jira, or Linear issue reference.
gplay-team
Developer account members and permissions with gplay team. Use when inviting or off-boarding a member, auditing what a member can do, granting per-app access, or looking up a permission alias or role bundle (team permissions, offline).