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 pipeline-health-to-owned-actiongit 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/pipeline-health-to-owned-action)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/pipeline-health-to-owned-action"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/pipeline-health-to-owned-action/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/pipeline-health-to-owned-action"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/pipeline-health-to-owned-action.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.00022 | $0.00701 |
| Opus 5.5 | $0.00009 | $0.00280 |
| Sonnet 5.5 | $0.00004 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
pipeline-health-to-owned-action 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Health to Owned Action
Outcome
Turn one stale B2B opportunity in comparable CRM snapshots into an owned next-step decision after checking its current activity and contact state. A pipeline exception is not a forecast, permission to contact a buyer, or proof that CRM changed.
When to use
Use when a sales manager needs to understand a stale opportunity and ask the seller for an exact next decision. Pipeline Analyst owns the snapshot comparison; Deal Follow-through Coordinator owns current-state review and the seller action register. Run one opportunity per handoff; aggregate counts can be reported only after each bounded record is checked.
Discovery and user direction
Inspect existing Sales Crews, CRM account and pipeline, prior/current snapshot coverage, stage and currency definitions, stale rule, seller owner, current opportunity/activity source and contact policy. Show a concrete proposal before Builder configures it. A single snapshot supports a current-state brief, but this route needs two comparable snapshots.
Required inputs
Bind tenant, CRM account, pipeline, reporting window, exact opportunity, snapshot IDs and revisions, stage and amount/currency fields, stale threshold, activity and contact source, seller owner and approval policy. Record gaps and changed definitions.
Plan and AgentWorks tools
Create Pipeline exception, blocking validation, Deal current-state review and blocking validation steps. Pipeline emits pipeline-exception-brief/v1 with an exact opportunity, comparable snapshots, source IDs, stale calculation and limits. Deal receives the validated artifact, re-reads current CRM, activity and prior contact, and emits deal-action-register/v1 with an unsent, unexecuted seller decision. A CRM write, message or meeting change is a separate exact-object approved route with a provider receipt.
Knowledge and persistence
Save snapshot and opportunity IDs, definitions, stale rule, activity source revision, action key, seller decisions and any exact provider receipts. On repeats, re-read current state, compare like windows, preserve prior decisions and retire superseded suggestions.
What ships with it
8 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/deal-action-register.json 1.2 KB
- examples/invalid-deal-action-register.json 1.2 KB
- examples/pipeline-exception-brief.json 1.2 KB
- playbook.json 4.3 KB
- references/team-and-handoffs.md 2.6 KB
- scripts/test_validate_handoff.py 3.6 KB runs code
- scripts/validate_handoff.py 8.1 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 · 48 lines · 22 tokens per session scan A ee5462545147
pipeline-health-to-owned-action is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 22 tokens to every session and 701 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…