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 skills/stoa-platform/stoa/fill-cyclenpx skills add stoa-platform/stoa --skill fill-cyclegit clone --depth 1 https://github.com/stoa-platform/stoaWrote 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/stoa-platform/stoa/fill-cycle)<a href="https://agentmods.dev/skills/stoa-platform/stoa/fill-cycle"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/fill-cycle.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 | $0.00023 | $0.02373 |
| Opus 5 | $0.00012 | $0.01187 |
| Sonnet 5 | $0.00005 | $0.00475 |
| Haiku 4.5 | $0.00002 | $0.00237 |
Grade A, and why
fill-cycle 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 4d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fill Cycle — Velocity Pipeline
Load the current Linear cycle, compute the capacity gap against proven velocity, scan 4 backlog sources, and propose a ranked fill plan.
Target: $ARGUMENTS
Linear Label IDs (cached)
| Label | ID |
|---|---|
roadmap (parent group — NOT assignable to issues) |
<LABEL_ID_ROADMAP> |
roadmap:gateway |
<LABEL_ID_ROADMAP_GATEWAY> |
roadmap:dx |
<LABEL_ID_ROADMAP_DX> |
roadmap:platform |
<LABEL_ID_ROADMAP_PLATFORM> |
roadmap:community |
<LABEL_ID_ROADMAP_COMMUNITY> |
roadmap:observability |
<LABEL_ID_ROADMAP_OBSERVABILITY> |
Step 0: Determine Mode
| Argument | Mode | Description |
|---|---|---|
| (empty) | Interactive | Show fill plan, ask before promoting |
--check |
Read-only | Compute capacity report only, no writes (CI-safe) |
--auto |
Auto-promote | Promote quick wins automatically, suggest council for MEGAs |
--theme <name> |
Themed fill | Filter candidates by roadmap theme + optional Notion search |
Step 1: Fetch Current Cycle from Linear
linear.list_cycles(teamId: "<LINEAR_TEAM_ID>")
Identify the current cycle (type "current" or date range containing today).
Extract: cycle_id, name, start, end, scopeTotal, completedTotal.
Then fetch all issues in the cycle:
linear.list_issues(
team: "<LINEAR_TEAM_ID>",
cycle: "<cycle_id>",
first: 50
)
Compute:
cycle_days= (end - start).daysdays_remaining= (end - today).dayspts_committed= sum of all issue estimates in cyclepts_done= sum of estimates for Done/Canceled issues
Step 2: Read Velocity Baseline
Read .claude/state/velocity.json.
Extract:
rolling_avg_pts_per_day=rolling_avg_3.pts_per_daytarget_utilization(default 0.80)
Compute capacity gap:
capacity = rolling_avg_pts_per_day × cycle_days
target = capacity × target_utilization
gap = target - pts_committed
If gap <= 0: report "Cycle is fully loaded" and stop (unless --check which still reports).
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.
- 4d ago First seen · 277 lines · 23 tokens per session scan A c7e9bea9cda7
fill-cycle is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 2,373 once invoked, about $0.0001 per session on Opus 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
lyrik
Security assessment of a codebase — minimal mode for runner validation.
librarian
Read-only retrieval over the daily-digest kept set. Slash-invoke with /librarian ; returns items verbatim with citations.
notes
Create and manage text notes in the workspace.
tdx-assets
Look up staff devices, assets, and locations in TeamDynamix (TDX). Given a list of names, emails, or partial identifiers, resolve each person and return the assets assigned to them with location, model, ownership type, and status. Read-only.
aggregator
Daily fetch from a fixed public allowlist; score against the user's interests file; cluster into themes; push the digest to the configured channel.
csv-tools
Parse and analyze CSV data.