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 agentmods add skills/chrono-meta/forge-harness/return-path-gatenpx skills add chrono-meta/forge-harness --skill return-path-gategit clone --depth 1 https://github.com/chrono-meta/forge-harnessWrote 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/chrono-meta/forge-harness/return-path-gate)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/return-path-gate"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/return-path-gate.svg" alt="Measured on agentmods" 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 | $0.00091 | $0.03341 |
| Opus 5 | $0.00046 | $0.01670 |
| Sonnet 5 | $0.00018 | $0.00668 |
| Haiku 4.5 | $0.00009 | $0.00334 |
Grade A, and why
return-path-gate 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 4d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
return-path-gate — Skill Chain Closure Audit
A skill chain is CLOSED when the callee's verdict folds back into the caller's decision logic. A chain is OPEN (fire-and-forget) when the caller dispatches a downstream skill but proceeds independently of the result.
This skill audits §Chains and §Done When sections across SKILL.md files to detect OPEN chains and prescribe specific closures.
Role Separation from harness-doctor
| Dimension | harness-doctor | return-path-gate |
|---|---|---|
| What it checks | Structural completeness (files, references, line counts, drift) | Chain closure compliance (caller/callee verdict handoff) |
| Core question | "Are the required harness files present and consistent?" | "Does the caller wait for the callee's verdict?" |
| Failure mode detected | Missing CLAUDE.md, broken refs, complexity drift | Fire-and-forget chains, unverified CONDITIONAL_PASS conditions |
| Output | L1–L5 structural health report | CLOSED/OPEN chain table with fix prescriptions |
Trigger Phrases
| Phrase | Situation |
|---|---|
| "chain audit", "chain closure audit" | Full scan of all skill chains in plugins/ |
| "return-path check", "return-path gate" | Explicit compliance audit |
| "fire-and-forget detection", "fire-and-forget chain" | Targeting known anti-pattern |
| "skill chain compliance" | Pre-flight check before pipeline execution |
| "does this skill wait for verdict" | Single-skill targeted check |
| "check chains in [skill-name]" | Scoped audit on a named skill |
/return-path-gate |
Explicit call |
Audit Scope Options
| Flag | Scope | When to use |
|---|---|---|
--skill [name] |
Single named skill | Targeted check during development |
--all |
All SKILL.md files under plugins/ |
Full compliance sweep |
--pr |
Skills changed relative to origin/main |
Pre-PR gate mode (worktree-aware) |
| (default) | Modified + newly added SKILL.md files in working tree | Pre-commit gate mode |
Execution Steps
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.
- 4d ago First seen · 287 lines · 91 tokens per session scan A c7d8af4eb22c
return-path-gate is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 3,341 once invoked, about $0.0005 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-30.
Other skills, from other repositories
lint-paper
Check paper directories for completeness, format compliance, and index consistency. Run on a single paper or --all for the entire collection.
encapsulation
This skill should be used when the user asks to "audit plugin encapsulation", "check self-containment semantics", "find contributor-knowledge assumptions", or invokes /encapsulation. Reviews LLM-facing prose in this project's plugin SKILL.md files and plugin description metadata for Plugin Encapsulation compliance…
review-rust
Perform critical Rust code reviews covering correctness, edition 2024 compliance, error handling, API design, async pitfalls, and dependency hygiene. ALWAYS use this skill when the user wants to review, audit, or critically evaluate Rust code — whether that's a PR diff, a specific crate or module, a cross-cutting…
multi-wordcheck
基于官方违禁词库，覆盖公众号、小红书、抖音三大平台审核标准，支持文案、文件、图片、链接多形式输入，快速输出违禁词标记与上下文替换建议。.
compliance-check
Run a content draft against the compliance knowledge base in brain/compliance/ and return PASS or FAIL with exact concerns. Use on every draft before it reaches output/drafts/ or Mai Marketing Machine, and whenever the owner says "compliance check", "is this compliant", or "check this post". No draft proceeds without…
check-the-licence-before-you-copy
Use before pulling someone else's code, skills, prompts or configuration into your project, and before publishing anything that contains them. Turns "it was on GitHub" into an obligation you can actually meet.