agentmods.dev

handing-off-to-engineering

handing-off-to-engineering is a skill for Claude Code from richfrem/agent-plugins-skills. It costs 122 tokens per session (810 once invoked), scanned A, original, MIT.

A handoff and technical-discovery process for sending explored business work to engineers. It assesses risk, prepares a package, and can produce a read-only report about the codebase.

In plain words
What is it for?
Use it to prepare an engineering handoff, classify risk, record unresolved questions, or create a technical diagnostic brief without changing source code.
Why use it?
It reduces missing requirements and unsupported claims when moving from business exploration into engineering work.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is python3 ../running-exploration-cycle/scripts/validate_phase_gate.py 4.

Part of the agent-exploration-cycle plugin — 5 skills, 4 agents shipped together

not rated 7repo yesterday A scan 122 tokens original MIT

Good fit Use it to prepare an engineering handoff, classify risk, record unresolved questions, or create a technical diagnostic brief without changing source code.

Compare 6 skills from other repositories ↓
View source ↗ richfrem/agent-plugins-skills
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/richfrem/agent-plugins-skills
agentmods
npx agentmods add skills/richfrem/agent-plugins-skills/handing-off-to-engineering

Made for: Claude Code.

Or install agent-exploration-cycle, the plugin that ships this one along with the rest of its 5 skills, 4 agents.

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.

agentmods badge for handing-off-to-engineering

README.md
[![agentmods](https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/handing-off-to-engineering/github.svg)](https://agentmods.dev/skills/richfrem/agent-plugins-skills/handing-off-to-engineering)
Your own site
<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/handing-off-to-engineering"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/handing-off-to-engineering/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.

agentmods 80×15 button for handing-off-to-engineering

Your own site · 80×15
<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/handing-off-to-engineering"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/handing-off-to-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 810 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.
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.1 $0.00122 $0.00810
Opus 5.5 $0.00049 $0.00324
Sonnet 5.5 $0.00024 $0.00162
Haiku 4.5 $0.00012 $0.00081

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

Security

Grade A, and why

handing-off-to-engineering 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 2d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/technical_diagnostic_engine.py, scripts/test_technical_diagnostic_engine.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/agent-exploration-cycle/.apm/skills/handing-off-to-engineering/SKILL.md · 61 lines

How it starts

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

Handing Off to Engineering

Shared exit for all paths: handoff-junction.mmd.

Contents

Constraints

  • Source grounding: never invent requirements; cite the capture for every major claim.
  • One Tier-3 rule (handoff guide): Tier 3 means a formal engineering cycle, never "deploy after review". Write tier3-risk-summary.md first and put it at the top of the package. Q5 alone is Tier 2 with ethics review.
  • Final package: no [NEEDS HUMAN INPUT]; unresolved items become [UNCONFIRMED] with a reason plus a ## Deferred Gaps list; every readiness check carries evidence; emit PHASE 4 COMPLETE.
  • Technical discovery is read-only: no source changes outside exploration/.
  • Control plane: for structured engineering name the os-control-intake skill; do not import or path into agent-agentic-os.
  • Pick runtime and model through the cli-agent skill; never name models.

Quick start

From this skill's folder:

python3 scripts/technical_diagnostic_engine.py --task-id <id> --title "<title>" --output exploration/DIAGNOSTIC_BRIEF.md
python3 ../running-exploration-cycle/scripts/validate_phase_gate.py 4

Workflow

  1. Scribe: fill any missing capture via capturing-business-requirements.
  2. Assess the five risk questions; choose the delivery path and format; write exploration/handoffs/handoff-package.md.
  3. Placeholder sweep, then reader test (three blocker questions for the consumer).
  4. Validate, get SME approval, route: self-deploy, review, formal engineering via os-control-intake, or defer.
  5. Re-entry: quote the engineering ambiguity verbatim, draft a new session brief for running-exploration-cycle.

Verification

python3 -m pytest scripts -q

Acceptance criteria: acceptance-criteria.md.

Read the full file on GitHub · 61 lines

Files

What ships with it

12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 61 lines · 122 tokens per session scan A 841852d5bdad

Subscribe to this mod's changes

handing-off-to-engineering is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 122 tokens to every session and 810 once invoked, about $0.0005 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-10-24.

PlanningProject managementagent-evaluationagent-orchestrationagentic-control-planeagentic-osagentic-workflowsai-agent-governance
Related

Other skills, from other repositories

triage

Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…

arcee-ai/nac · 65 tokens

factory-handoff

Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.

watt-mind/factory · 47 tokens

ticket-spec

Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.

watt-mind/factory · 45 tokens

mindforge-session-report

Generate a session report with token usage estimates, work summary, and outcomes.

sairam0424/MindForge · 19 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens