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-update-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-update-ticket)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-ticket"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-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-update-ticket"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00134 | $0.03229 |
| Opus 5 | $0.00067 | $0.01614 |
| Sonnet 5 | $0.00027 | $0.00646 |
| Haiku 4.5 | $0.00013 | $0.00323 |
Grade A, and why
aid-update-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 9d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Ticket
aid-update-ticket <part> [<connector>:]<ticket-id> <content> mutates one named part of an
existing ticket in whatever issue-tracker connector resolves for it — description (REPLACE),
comment (APPEND), or status (SET) — after showing the user the exact change and waiting for
explicit confirmation. It is the third of the three peer ticket-tracker skills alongside
aid-read-ticket (fetch/display, non-destructive) and aid-create-ticket (file a new ticket).
Absent from the mandatory pipeline flow. Like aid-ask and aid-set-connector, this is
an optional, on-demand utility skill — no phase gate references it, no shortcut-catalog.yml
entry, no work-NNN scaffold, no per-skill STATE.yml; it is invoked directly by name.
Shared reference — implemented here, not restated. The connector-resolution ladder, this
skill's own grammar row, and the write preview/confirm-gate convention all live once in
.claude/aid/templates/connectors/ticket-resolution.md
(the same DRY home aid-read-ticket and aid-create-ticket point to). This file never
re-describes the ladder or the generic confirm convention inline — it only spells out the parts of
the contract that are specific to this skill: the description | comment | status mutation
semantics, per-part LOAD-CONTEXT, and status transition validation.
No repo write, ever. allowed-tools carries no Write/Edit — this skill persists nothing
locally. The only write it ever performs is the single host-MCP mutation call at WRITE, and only
after an explicit confirm.
Pre-flight
- Confirm the invocation shape before anything else. Fewer than three whitespace-separated
pieces (missing
<part>, missing the ref, or no<content>after it) → print the usage line and exit (ticket-resolution.md§ "Grammar-Parse Conventions" — theaid-askpre-flight pattern):Usage: aid-update-ticket <part> [<connector>:]<ticket-id> <content> Example: aid-update-ticket status jira:PROJ-9 "In Progress" <part>MUST be one of the closed enumdescription | comment | status. Anything else — a typo, a synonym, an unsupported word — is rejected with the same usage line above, never coerced and never guessed at. This check runs before any connector resolution or MCP call.
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.
- 9d ago First seen · 229 lines · 134 tokens per session scan A d5c4ebc584bd
aid-update-ticket is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 134 tokens to every session and 3,229 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.