What is aid-read-ticket?

A read-only tool that fetches and displays one ticket from the project's connected issue tracker.

Use it during triage, before starting work, or when checking a ticket referenced by a change.

It gives you the ticket's current fields without changing the ticket or starting a larger workflow.

aid-read-ticket — Skill for Claude Code by AndreVianna/aid-methodology

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.

Any agent

npx skills add AndreVianna/aid-methodology --skill aid-read-ticket

Clone the repo

git clone --depth 1 https://github.com/AndreVianna/aid-methodology

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-read-ticket/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-read-ticket)

Your own site

<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.

Your own site · 80×15

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

Per session 150 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,358 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

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.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00150	$0.02358
Opus 5.5	$0.00060	$0.00943
Sonnet 5.5	$0.00030	$0.00472
Haiku 4.5	$0.00015	$0.00236

Measured 26d ago against content hash 0c2455022a7d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 26d 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.

.agents/skills/aid-read-ticket/SKILL.md · 189 lines

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 .aid/runtime/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 — the aid-read-ticket row.
Confirm gate: ticket-resolution.md § Write Preview + Confirm Gate — states plainly that read never 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:

Read the full file on GitHub · 189 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.

26d ago Changed 0c2455022a7d
2mo ago First seen · 189 lines · 150 tokens per session scan A 5c124d2bccb1

Subscribe to this mod's changes

aid-read-ticket is a skill published in the GitHub repository AndreVianna/aid-methodology (6 stars, last pushed 11d ago), licensed MIT. It adds 150 tokens to every session and 2,358 once invoked, about $0.0006 per session on Opus 5.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.

Project management

aid-read-ticket next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
aid-read-ticketAndreVianna/aid-methodology	Skill	6	11d ago	MIT	A	150	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code