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 manishiitg/coding-agent-loop --skill signed-deal-to-onboarding-handoffgit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/signed-deal-to-onboarding-handoff)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/signed-deal-to-onboarding-handoff"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/signed-deal-to-onboarding-handoff/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/manishiitg/coding-agent-loop/signed-deal-to-onboarding-handoff"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/signed-deal-to-onboarding-handoff.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.00033 | $0.00643 |
| Opus 5.5 | $0.00013 | $0.00257 |
| Sonnet 5.5 | $0.00007 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
signed-deal-to-onboarding-handoff 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 20d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Signed Deal to Onboarding Handoff
Outcome
Give Customer Success the purchased scope, agreed first result, target date and owner for one signed account. Acceptance requires current contract and entitlement checks; it does not prove onboarding or first value.
When to use
Use before New Customer to First Value when Sales and CS have distinct owners or access. For self-serve accounts, start onboarding from an authorized subscription source.
Discovery and user direction
Builder inspects existing Sales and CS Crews, CRM, agreement, entitlement and onboarding route. Propose reuse or reviewed creation and each Crew's access. Ask for missing owner or policy choices. Installation leaves setup pending.
Required inputs
Bind tenant, CRM account, opportunity, customer account, executed contract/revision, purchased scope, first-value goal/date, Sales and CS owners, entitlement rule, current sources and prior handoff keys. Conflicting CRM notes stop acceptance.
Plan and AgentWorks tools
Workflow steps: Sales reads CRM and agreement, emits sales-cs-handoff/v1, then a blocking validator runs. CS re-reads contract and entitlement, emits onboarding-acceptance/v1, and validates the pair. The receiving owner accepts or returns it with a reason. An accepted artifact may feed New Customer to First Value, whose validators still apply.
Knowledge and persistence
Keep stable handoff key, IDs, source revisions, first-value rule, decisions, validation and prior handoffs. Re-read sources before retrying. Changed contract or owner starts a new review.
Validation and reporting
The validator checks execution, identity, revision, scope, provisioning, duplicate keys, entitlement, owner receipt and chronology. Fictional accepted and needs resolution cases pass; false acceptance fails. The reporting dashboard separates pending, needs resolution and accepted, with blockers and owner.
What ships with it
10 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.
- examples/invalid-onboarding-acceptance.json 1.3 KB
- examples/needs-resolution.json 1.2 KB
- examples/onboarding-acceptance.json 1.3 KB
- examples/onboarding-register-from-accepted.json 1.2 KB
- examples/sales-cs-handoff.json 1.1 KB
- playbook.json 4.3 KB
- references/team-and-handoffs.md 2.6 KB
- scripts/test_validate_handoff.py 4.3 KB runs code
- scripts/validate_handoff.py 6.5 KB runs code
- SETUP.json 2.6 KB
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.
- 20d ago First seen · 49 lines · 33 tokens per session scan A eb95a2a320fe
signed-deal-to-onboarding-handoff is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 33 tokens to every session and 643 once invoked, about $0.0001 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-09-27.
Other skills, from other repositories
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
goga-task-by-specifying
Interactive task formulation from a raw request.
goga-cell-go
Golang rules for implementing CODEMANIFEST contracts.
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…