verify-mega

A checklist for closing MEGA tickets, which are larger Linear tickets made up of several sub-tickets or phases.

In plain words
What is it for?
Use it to verify one MEGA ticket or audit MEGA tickets closed during the previous seven days.
Why use it?
It checks that the component work, pull requests, and live verification are complete before the parent ticket is marked done.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/stoa-platform/stoa/verify-mega
Any agent
npx skills add stoa-platform/stoa --skill verify-mega
Clone the repo
git clone --depth 1 https://github.com/stoa-platform/stoa

Made for: Claude Code, Codex.

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,317 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 8987f5a85432, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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
.claude/skills/verify-mega/SKILL.md · 144 lines

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 $ARGUMENTS is --all-done-7d: Audit mode — scan all MEGAs marked Done in last 7 days
  • If $ARGUMENTS is CAB-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 children
  • children.nodes[] — list of sub-tickets with id, identifier, state.name, estimate
  • estimate — 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-XXXX first."

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" or state.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.dev or curl -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

Read the full file on GitHub · 144 lines

Changes

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.

  1. 3d ago First seen · 144 lines · 26 tokens per session scan A 8987f5a85432

Subscribe to this mod's changes

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.