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/generate-backlognpx skills add stoa-platform/stoa --skill generate-backloggit 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/generate-backlog)<a href="https://agentmods.dev/skills/stoa-platform/stoa/generate-backlog"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/generate-backlog.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.00030 | $0.04146 |
| Opus 5 | $0.00015 | $0.02073 |
| Sonnet 5 | $0.00006 | $0.00829 |
| Haiku 4.5 | $0.00003 | $0.00415 |
Grade A, and why
generate-backlog 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 3d 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Backlog — MEGA Ticket Pipeline
Scan the codebase and roadmap files, GROUP findings by component/theme into MEGA tickets (20-40 pts each, with phases and binary DoD), deduplicate against Linear, and optionally batch-create to maintain a 400+ pt backlog stock.
Philosophy: 10 MEGA tickets at 30 pts > 100 micro-tickets at 3 pts. Each ticket = a meaningful feature or improvement arc, not a single file fix.
Target: $ARGUMENTS
Linear IDs (cached)
| Entity | ID |
|---|---|
| Team (CAB-ING) | <LINEAR_TEAM_ID> |
| Project (STOA Platform) | <LINEAR_PROJECT_ID> |
| Assignee (<PRIMARY_ASSIGNEE>) | <LINEAR_ASSIGNEE_ID> |
Label IDs
| Label | ID |
|---|---|
roadmap (parent — NOT assignable) |
<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> |
Instance Label IDs (parallel dispatch)
| Label | ID | Components |
|---|---|---|
instance:backend |
<LABEL_ID_INSTANCE_BACKEND> |
cp-api, operator, infra, docs |
instance:frontend |
<LABEL_ID_INSTANCE_FRONTEND> |
cp-ui, portal, shared |
instance:auth |
<LABEL_ID_INSTANCE_AUTH> |
keycloak, IAM |
instance:mcp |
<LABEL_ID_INSTANCE_MCP> |
stoa-gateway |
instance:qa |
<LABEL_ID_INSTANCE_QA> |
e2e, tests |
Step 0: Determine Mode
| Argument | Mode | Description |
|---|---|---|
(empty) / --scan |
Scan | Read-only report, 0 Linear writes |
--create |
Create | Batch-create MEGA tickets on Linear (8-15 writes) |
--theme <name> |
Themed scan | Filter candidates by roadmap theme |
Default is --scan (safe, CI-compatible).
Step 1: Inventory — Current Backlog Depth
Fetch all backlog issues (no cycle) from Linear:
linear.list_issues(
team: "<LINEAR_TEAM_ID>",
first: 100
)
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.
- 3d ago First seen · 397 lines · 30 tokens per session scan A 2e5b484e5d35
generate-backlog is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 4,146 once invoked, about $0.0002 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.