agentmods.dev

write-handover

A handover writer that creates a plain-language support note covering the symptom, cause, change, scope, workaround, and QA steps.

In plain words
What is it for?
Use it for support, bug, or incident tickets that need a non-technical explanation and numbered verification steps.
Why use it?
It lets QA and the person who reported a problem understand and verify the result without reading code.

Skill for Claude CodeCodex

1 10d ago A scan 61 tokens original MIT
View the source file matheusPavaneli/workbench
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.

agentmods
npx agentmods add skills/matheuspavaneli/workbench/write-handover
Any agent
npx skills add matheusPavaneli/workbench --skill write-handover
Clone the repo
git clone --depth 1 https://github.com/matheusPavaneli/workbench

Made for: Claude Code, Codex.

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 630 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00061 $0.00630
Opus 5 $0.00030 $0.00315
Sonnet 5 $0.00012 $0.00126
Haiku 4.5 $0.00006 $0.00063

Measured yesterday against content hash cd93a3a9f324, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

write-handover 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 yesterday.

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.

skills/write-handover/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

write-handover

python "${CLAUDE_PLUGIN_ROOT}/lib/wb.py" <args>

The audience is not engineering. A QA lead has to validate this without reading the diff, and whoever raised the ticket has to understand what happened without knowing the codebase exists.

Steps

  1. Read the ticket and the plan. .workflow/<KEY>/triage.json for what was reported and in whose words; sdd get <KEY> --section summary and --section evidence for what was actually wrong.

  2. Fill the handover block in sdd.json:

    Field
    symptom_plain what the reporter saw, in their words
    cause_plain why it happened, one sentence a non-engineer can repeat
    fix_plain what changes for them
    scope who was affected, since when, how many
    workaround what to do until it ships, or none
    qa_steps numbered steps, ending in the expected result
    release_note one line, if the repo keeps a changelog

  3. Write qa_steps as something a person can follow. Start from a state they can reach, name the exact input, and end with what they should see. "Test the coupon flow" is not a step. "Apply coupon SUMMER24, expired yesterday → the order is refused with a validation message and no charge appears in Stripe" is.

  4. Render it. sdd handover <KEY> writes .workflow/<KEY>/handover.md for pasting into the ticket.

  5. Say what is not covered. If the fix addresses the reported symptom but not a related case the reporter may hit, that belongs here, not discovered later.

Rules

  • No jargon, no paths, no function names, no commit hashes. If it cannot be said without them, it is not understood well enough to hand over.
  • Do not claim a cause you could not demonstrate. "Under investigation" is a legitimate handover; a confident wrong cause is not.
  • The scope is a fact, not a comfort. If you do not know how many users were affected, say that rather than implying it was few.
  • Nothing beyond what is needed. Five short answers and the steps. No restating the ticket back, no apology, no summary of the summary.

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

  1. yesterday First seen · 56 lines · 61 tokens per session scan A cd93a3a9f324

Subscribe to this mod's changes

write-handover is a skill published in the GitHub repository matheusPavaneli/workbench (1 stars, last pushed 10d ago), licensed MIT. It adds 61 tokens to every session and 630 once invoked, about $0.0003 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-08-31.

Code reviewDebuggingDeveloper WorkflowTestingazure-devopsclaude-codeclaude-code-pluginjira
Related

Other skills, from other repositories

integration-rule-engine

A declarative routing engine that turns ticket / error attributes (reporter, label, project, area path, error class, environment) into a tag + AI agent + priority assignment, so cross-source workflows ("security tickets always go to the OWASP reviewer") stay out of code and in user-editable rules.

aozyildirim/Agena · 67 tokens

stale-ticket-triage

Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.

aozyildirim/Agena · 57 tokens

azure-devops

Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…

sanjay3290/ai-skills · 105 tokens

apple-container

Apple's open-source container CLI to build, run, and manage OCI/Linux containers as lightweight per-container VMs on Apple-silicon macOS — no Docker daemon required. Use when the user mentions the container CLI, "apple container", running or building containers on macOS without Docker/Podman, container run, container…

sanjay3290/ai-skills · 146 tokens

atlassian

Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via…

sanjay3290/ai-skills · 96 tokens

elevenlabs

Convert documents and text to audio using ElevenLabs text-to-speech. Use this skill when the user wants to create a podcast, narrate a document, read aloud text, generate audio from a file, or convert text to speech.

sanjay3290/ai-skills · 51 tokens