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 mostafa-drz/claude-skills --skill post-ticket-summarygit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/post-ticket-summary)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/post-ticket-summary"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/post-ticket-summary/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/mostafa-drz/claude-skills/post-ticket-summary"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/post-ticket-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00045 | $0.01415 |
| Opus 5.5 | $0.00018 | $0.00566 |
| Sonnet 5.5 | $0.00009 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
post-ticket-summary 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 1mo 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post Ticket Summary
Add a structured implementation summary comment to a Linear issue after completing work.
Preferences
Read ~/.claude/skills/post-ticket-summary/preferences.md using the Read tool. If not found, no preferences are set.
Context
On startup, use Bash to detect: current git branch, recent commits (git log --oneline -20), and repo name (gh repo view --json nameWithOwner -q .nameWithOwner). Skip any that fail.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete~/.claude/skills/post-ticket-summary/preferences.md, confirm, stop--preview <issue-id>→ show comment without posting then stop--minimal <issue-id>→ use minimal template- anything else → post summary
Help
Post Summary — Document implementation on a Linear issue
Usage:
/post-ticket-summary <issue-id> Post full summary
/post-ticket-summary --preview <issue-id> Show without posting
/post-ticket-summary --minimal <issue-id> Short summary (skip architecture/reuse)
/post-ticket-summary config Set template preferences
/post-ticket-summary reset Clear preferences
/post-ticket-summary help This help
Examples:
/post-ticket-summary AIS-810
/post-ticket-summary --preview AIS-810
/post-ticket-summary --minimal AIS-810
What it does:
1. Reads the Linear issue and codebase
2. Analyzes recent commits and changed files
3. Builds structured summary comment
4. Posts to the Linear issue
Current preferences:
(shown above under Preferences)
Config
Use AskUserQuestion:
Q1 — "Default template?" (full (default), minimal) Q2 — "Which sections to include?" (multiSelect: true)
- Implementation summary
- Key decisions / architecture
- What was reused
- How to test
- Notes
Q3 — "Auto-detect issue from branch?" (Yes (default), No — always ask)
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.
- 1mo ago Changed · +3 lines 15781b5a6917
- 1mo ago First seen · 233 lines · 45 tokens per session scan A eb783982fdc5
post-ticket-summary is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,415 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
wrap-up
Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/ /log.md or career-vault/log.md, one entry per project touched, never to new-client. Use when the student…
pick-up
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when the student says pick up, where did I…
scrum-master-agent
Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting.
shipkit-user-instructions
Use when there are manual tasks the user must complete. Triggers: 'create task', 'track TODO', 'user needs to', 'manual step required'.
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
shipkit-orchestrate
Core automation engine. Drives a set of steps to a confirmed ground-truth bar via a main-session delegate → reconcile → re-dispatch loop. Phase skills (build, review, direction) call it; can also run directly. Two modes: autonomous (run to done unattended) and steered (coordinate, surface to user). Triggers: invoked…