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 AndreVianna/aid-methodology --skill aid-read-ticketgit clone --depth 1 https://github.com/AndreVianna/aid-methodologyWrote 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/andrevianna/aid-methodology/aid-read-ticket)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-read-ticket"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-read-ticket/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/andrevianna/aid-methodology/aid-read-ticket"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-read-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 156 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00150 | $0.02366 |
| Opus 5 | $0.00075 | $0.01183 |
| Sonnet 5 | $0.00030 | $0.00473 |
| Haiku 4.5 | $0.00015 | $0.00237 |
Grade A, and why
aid-read-ticket 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 8d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read Ticket
aid-read-ticket [<connector>:]<ticket-id> fetches and displays one ticket's fields from
whatever issue tracker the project has integrated. It is tool-agnostic — it never names a
specific tracker, and instead resolves which one to use through AID's connector layer.
Not a numbered pipeline phase. Optional, on-demand utility skill, a peer of aid-ask /
aid-set-connector — no phase gate references it, no shortcut-catalog.yml entry, no
work-NNN scaffold, no STATE.yml of its own.
Single-shot, no confirm. One pass: parse → resolve → fetch → display → exit. Reading is
non-destructive (feature-001 AC-1) — it never prompts for a write, regardless of how many
connectors are catalogued. The connector-choice AskUserQuestion (State 2, below), when it
fires, is a resolution branch, never a write-confirmation gate.
Shared reference — read this first
The connector-resolution ladder, the [<connector>:]<ticket-id> grammar-parse rule, and the
write-preview/confirm conventions all live once, in
.claude/aid/templates/connectors/ticket-resolution.md
— the single shared home for all three ticket skills (aid-read-ticket, aid-create-ticket,
aid-update-ticket). This SKILL.md implements that reference by pointer only; nothing below
re-describes the ladder's own validation logic, the grammar's own tokenizing rule, or the confirm
convention — it only names which of the reference's outcomes this skill's own states route to.
- Ladder:
ticket-resolution.md § Connector-Resolution Ladder. - Grammar:
ticket-resolution.md § Grammar-Parse Conventions— theaid-read-ticketrow. - Confirm gate:
ticket-resolution.md § Write Preview + Confirm Gate— states plainly thatreadnever prompts; there is no gate to implement here.
Pre-flight
Confirm exactly one positional argument was supplied. If /aid-read-ticket is invoked with no
argument (or an empty/whitespace-only one), print the argument-hint usage line and exit without
fetching anything — the aid-ask pre-flight pattern; ticket-resolution.md's "Missing/empty
required args" rule:
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.
- 8d ago First seen · 189 lines · 150 tokens per session scan A 5c124d2bccb1
aid-read-ticket is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 150 tokens to every session and 2,366 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.