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/verify-meganpx skills add stoa-platform/stoa --skill verify-megagit clone --depth 1 https://github.com/stoa-platform/stoaWhat 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.00026 | $0.01317 |
| Opus 5 | $0.00013 | $0.00659 |
| Sonnet 5 | $0.00005 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
verify-mega 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **API changes**: `curl -s https://api.gostoa.dev/health` → expect 200 How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify MEGA — $ARGUMENTS
Overview
Run all 5 MEGA Close Gates on a ticket (or audit all recently-closed MEGAs). Prevents false Dones on multi-phase tickets.
Mode Detection
- If
$ARGUMENTSis--all-done-7d: Audit mode — scan all MEGAs marked Done in last 7 days - If
$ARGUMENTSisCAB-XXXX: Single mode — verify one MEGA ticket
Step 1: Fetch MEGA Data
Single Mode
linear.get_issue("CAB-XXXX", includeRelations=true)
Extract:
title— verify contains[MEGA]or has childrenchildren.nodes[]— list of sub-tickets withid,identifier,state.name,estimateestimate— total points
If no children → report: "CAB-XXXX is not a MEGA (no children). Use standard close flow."
Audit Mode
linear.list_issues(
teamId: "<LINEAR_TEAM_ID>",
filter: { state: { name: { eq: "Done" } }, updatedAt: { gte: "<7 days ago>" } }
)
Filter results to only MEGAs (title contains [MEGA] or has children).
Run gates on each.
Step 2: Gate 0 — Decomposition Invariant
- Check:
children.nodes.length > 0 - Pass: MEGA has sub-tickets
- Fail: "MEGA has no sub-tickets. Run
/decompose CAB-XXXXfirst."
Step 3: Gate 1 — Per-Phase PR Evidence
For each child ticket in Done state:
linear.list_comments(issueId: "<child_id>")
Check that at least one comment contains PR # or PR [#.
- Pass: All Done children have PR evidence
- Fail: List children missing PR references: "CAB-XXXX: no PR evidence found"
Step 4: Gate 2 — All Sub-Tickets Done
Check each child's state.name:
- Pass: ALL children have
state.name == "Done"orstate.name == "Canceled" - Fail: List non-Done children with their current state:
CAB-1351: In Progress CAB-1352: Todo
Step 5: Gate 3 — Live Verification
Based on the MEGA's component scope:
- API changes:
curl -s https://api.gostoa.dev/health→ expect 200 - UI/Portal:
curl -s https://console.gostoa.devorcurl -s https://portal.gostoa.dev→ expect 200 - Gateway:
curl -s https://mcp.gostoa.dev/health→ expect 200 - Docs:
curl -s https://docs.gostoa.dev→ expect 200 - Cross-component: verify all affected endpoints
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 · 144 lines · 26 tokens per session scan A 8987f5a85432
verify-mega is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,317 once invoked, about $0.0001 per session on Opus 5. 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-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.