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 ai-analyst-lab/ai-analyst --skill close-the-loopgit clone --depth 1 https://github.com/ai-analyst-lab/ai-analystWrote 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/ai-analyst-lab/ai-analyst/close-the-loop)<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/close-the-loop"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/close-the-loop/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/ai-analyst-lab/ai-analyst/close-the-loop"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/close-the-loop.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.00248 | $0.02986 |
| Opus 5 | $0.00124 | $0.01493 |
| Sonnet 5 | $0.00050 | $0.00597 |
| Haiku 4.5 | $0.00025 | $0.00299 |
Grade A, and why
close-the-loop 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.
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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Close-the-Loop
Purpose
Ensure every analysis that includes a recommendation ends with a clear follow-up plan — who decides, what metric tracks success, when to check back, and what to do if the expected outcome doesn't materialize.
When to Use
Triggering Test (use this decision tree)
Ask yourself: "Has a specific recommendation or action item been made?"
- YES → Apply Close-the-Loop
- NO → Skip (even if a decision is needed, wait until the recommendation is formulated)
Apply this skill when:
- The analysis concludes with a recommendation ("we should do X")
- Root cause investigation identifies a fix ("deploy the hotfix", "roll back v3.2")
- Opportunity sizing recommends an investment ("invest 2 eng-months to recover $2.1M")
- Multiple options are presented and a decision is needed ("Option A vs B vs C")
- The analysis outputs action items that need tracking
Skip this skill when:
- Pure exploratory analysis with no recommendations ("interesting pattern, still investigating")
- User is asking whether to investigate ("should we look into this?" — this is premature, no recommendation yet)
- Questions about causality ("is this correlation or causation?" — wait until you recommend a course of action)
- Descriptive reports with no proposed actions ("here's what happened last quarter")
- Data quality assessments (unless they recommend fixes)
- Answering factual questions ("what was revenue last month?")
Instructions
The Close-the-Loop Checklist
Append this checklist to the end of every analysis report or presentation that includes a recommendation:
## Close the Loop
### Decision
- **Recommendation:** [What the analysis recommends]
- **Decision maker:** [Who will approve/reject this — name or role]
- **Decision deadline:** [When this needs to be decided by]
- **Decision made:** [ ] Yes / [ ] No / [ ] Deferred
- **Decision outcome:** [What was actually decided — fill in after]
### Success Tracking
- **Success metric:** [What metric will tell us the recommendation worked?]
- **Current baseline:** [What is the metric today?]
- **Target:** [What value do we expect if the recommendation works?]
- **Measurement window:** [How long after implementation before we evaluate?]
- **Data source:** [Where to pull the metric]
### Follow-Up
- **Check-in date:** [When to evaluate whether the recommendation worked]
- **Owner:** [Who is responsible for the follow-up check]
- **If successful:** [What's the next step — scale it, document it, move to next priority]
- **If unsuccessful:** [What's the fallback — investigate further, try alternative, accept the status quo]
- **If inconclusive:** [What additional data or time is needed before deciding]
### Analysis Provenance
- **Analysis date:** [When this analysis was completed]
- **Analyst:** [Who produced it]
- **Key assumptions:** [1-3 assumptions the recommendation depends on]
- **Confidence level:** [HIGH / MEDIUM / LOW]
- **What would change the recommendation:** [Under what conditions should we revisit]
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.
- 2d ago First seen · 263 lines · 248 tokens per session scan A a3eda9cb5b82
close-the-loop is a skill published in the GitHub repository ai-analyst-lab/ai-analyst (298 stars, last pushed 3d ago), licensed MIT. It adds 248 tokens to every session and 2,986 once invoked, about $0.0012 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-09-12.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
remove
Remove a deployed framework or addon from the current workspace.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…