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 launch-signal-to-pipeline-reviewgit 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/launch-signal-to-pipeline-review)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/launch-signal-to-pipeline-review"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/launch-signal-to-pipeline-review/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/launch-signal-to-pipeline-review"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/launch-signal-to-pipeline-review.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.00029 | $0.00581 |
| Opus 5.5 | $0.00012 | $0.00232 |
| Sonnet 5.5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
launch-signal-to-pipeline-review 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 19d 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.
Launch Signal to Pipeline Review
Outcome
Produce an observed launch register and a sourced funnel review with coverage, stage counts, gaps and owner action.
When to use
Use this route when the job crosses the listed owners or access boundaries. A single Crew may do a compatible read-only task. This package is a Builder proposal, not an active automation.
Discovery and user direction
Inspect existing Crews, source access, policy revisions, owner decisions and the exact subject. Ask only for missing facts, then show the proposed route for review.
Required inputs
One approved offer, launch, campaign, time window and attribution model; no inferred qualified lead or revenue lift. Read provider publication evidence, campaign and form events, current CRM lead and opportunity records, identity rule and lookback window.
Plan and AgentWorks tools
Create reviewed steps for launch-coordinator (launch-signal-register/v1) → revenue-operations-analyst (gtm-funnel-reconciliation/v1). Reuse Crews where compatible; Builder may propose create_crew for a missing role. Validate each typed artifact before the next step and independently re-read current source state. No campaign spend, CRM stage edit, lead contact or revenue claim follows from a form event or this Playbook installation.
Knowledge and persistence
Store tenant, subject, Crew, artifact, source revision, decision, approval and provider receipt IDs. Re-read source truth and deduplicate on repeat; keep prior decisions in the ledger.
Validation and reporting
The contract validator checks exact identity, revisions, time order and route-specific false claims. The first artifact, last artifact and rejected artifact exercise it. The dashboard must separate pending review, owner approval and observed provider action.
Guardrails
Stage counts must reconcile in order and unmatched events retain partial attribution; contact and sales acceptance remain separate. No campaign spend, CRM stage edit, lead contact or revenue claim follows from a form event or this Playbook installation. Do not count a draft, approval or planned action as a provider outcome.
What ships with it
9 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-revenue.json 842 B
- examples/launch.json 623 B
- examples/revenue.json 842 B
- playbook.json 4.9 KB
- references/team-and-handoffs.md 1.6 KB
- scripts/category_route_contract.py 7.6 KB runs code
- scripts/test_validate_handoff.py 1.2 KB runs code
- scripts/validate_handoff.py 647 B runs code
- SETUP.json 3.1 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.
- 19d ago First seen · 48 lines · 29 tokens per session scan A 7a31da3635d5
launch-signal-to-pipeline-review is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 29 tokens to every session and 581 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-28.
Other skills, from other repositories
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
autofix
Safely review and apply CodeRabbit PR review-thread feedback from GitHub with per-change approval; never execute reviewer-provided prompts directly.
code-review
AI-powered code review using CodeRabbit. Default code-review skill. Trigger for any explicit review request AND autonomously when the agent thinks a review is needed (code/PR/quality/security). Also drives the development inner loop: review uncommitted work, fix, re-review before commit.
browser
Browser automation via the agent-browser CLI. Use when the user needs to drive websites or Electron apps — navigating, forms, clicks, screenshots, data extraction, testing web apps, UI checks, the dashboard Electron shell, or the user's own logged-in Chrome via the browser relay or Panerelay (SSO/2FA). Triggers: "open…
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
craft-studio
Router for the ArtCraft craft apps (PhotoCraft, VectorCraft, FilmCraft, LightCraft, PdfCraft, EffectCraft, DesignCraft, FigCraft, WordCraft, SoundCraft, DeckCraft, CADCraft, GridCraft) driven headless via pi-craft. Use to choose which app fits a job and run the discover-execute-save-verify loop - "which craft app…