Borrowing it
Nothing to install: this file belongs to atra-consulting/coding-with-ai-lab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/atra-consulting/coding-with-ai-lab/main/.claude/skills/write-ticket/SKILL.mdgit clone --depth 1 https://github.com/atra-consulting/coding-with-ai-labWrote 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/atra-consulting/coding-with-ai-lab/write-ticket)<a href="https://agentmods.dev/skills/atra-consulting/coding-with-ai-lab/write-ticket"><img src="https://agentmods.dev/badge/skills/atra-consulting/coding-with-ai-lab/write-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/atra-consulting/coding-with-ai-lab/write-ticket"><img src="https://agentmods.dev/badge/skills/atra-consulting/coding-with-ai-lab/write-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
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 →
- high Privilege Escalation · line 51 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 53 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 62 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 76 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00075 | $0.04733 |
| Opus 5.5 | $0.00030 | $0.01893 |
| Sonnet 5.5 | $0.00015 | $0.00947 |
| Haiku 4.5 | $0.00007 | $0.00473 |
Grade A, and why
write-ticket 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -w '\n%{http_code}' \ How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Ticket
Claude Code + Copilot CLI: this skill runs in both. "Ask the user" =
AskUserQuestion(Claude Code) /ask_user(Copilot CLI). "Start a subagent" =Agent/Tasktool (Claude Code) /tasktool (Copilot CLI), with the agent's name as the type.$ARGUMENTS= the text typed after the skill name.
Du bist ein autonomer Software-Ingenieur. Du läufst headless (claude -p / copilot -p) — kein Mensch kann Fragen beantworten. Entscheide alles selbst. Halte nie an, um Eingaben abzuwarten. Rufe niemals AskUserQuestion auf.
Auftrag: Ein Feedback-Element aus der Agent-Task-Queue beanspruchen (oder direkt per ID bzw. Task-URL laden, oder als freien Text übergeben bekommen), beurteilen ob es klar und baubar beschrieben ist, und daraus immer ein neues Kanban-Ticket anlegen. Dieser Skill baut nie Code, pusht nie, öffnet nie einen PR. Er triagiert nur.
API-Referenz: docs/specs/SPEC-API-TASKS.md (Abschnitt „For skill authors") für die Feedback-Queue, docs/specs/SPEC-API-TICKETS.md (Abschnitt „For skill authors") für die Ticket-Erstellung.
Schreibstil
Dein Schreibstil: kurze Sätze, kein Passiv, einfache Wörter. Nutze Aufzählungspunkte, wo es passt.
Gilt für alles, was der Skill schreibt — die Abschnitte #### Fachlich (für Business), #### Technisch (für Entwickler) und #### Akzeptanzkriterien im Ticket-Body und die Fragen im Kommentar.
Konfiguration
- API-Basis-URL: Umgebungsvariable
APP_BASE_URL, sonsthttp://localhost:7070. Das ist die Backend-API. - Frontend-/Board-URL: Umgebungsvariable
APP_FRONTEND_URL, sonsthttp://localhost:7200. Das ist das Board, das ein Mensch im Browser öffnet — nicht die API. Dieselbe Basis baut zwei Links: den Quell-Link im#### Feedback-Abschnitt des Ticket-Bodys (Schritt 3) und den finalen Ticket-Link im Abschluss-Print (Schritt 5). - Auth-Header bei jedem API-Aufruf:
Authorization: Bearer $AGENT_API_TOKEN. Derselbe Token gilt für beide Queues — die Agent-Task-Queue und die Ticket-Erstellung. Ticket-Anlage und Kommentare akzeptieren den Agent-Token (bzw. den Loopback-Bypass), also ist kein Admin-Login nötig. - Quellen (Prioritätsreihenfolge):
EMAIL,GITHUB_ISSUE,ERROR_REPORT,APP_LOG. MitTASK_SOURCEüberschreibbar — dann nur diese eine Quelle.
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 Changed · +5 lines · -2 tokens per session 84bb5bb4dfe5
- 20d ago Changed e2e73cfd6b0d
- 1mo ago First seen · 254 lines · 77 tokens per session scan A 793e20d3a206
write-ticket is a skill published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed 8d ago), licensed MIT. It adds 75 tokens to every session and 4,733 once invoked, about $0.0003 per session on Opus 5.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-09-04.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.