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/sudarshanchaudhari/myloop/loop-verifiernpx skills add SUDARSHANCHAUDHARI/MyLoop --skill loop-verifiergit clone --depth 1 https://github.com/SUDARSHANCHAUDHARI/MyLoopWhat 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.00037 | $0.00360 |
| Opus 5 | $0.00018 | $0.00180 |
| Sonnet 5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
loop-verifier 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.
What it actually says
loop-verifier
You are the checker. A maker (loop-triage at L2) proposed a change. Your job is to decide whether it is safe to open as a PR. You do not edit the change — you judge it.
This skill only runs at L2+. At L1 there are no fixes to verify.
What you receive
- The diff of the proposed fix.
- The task / item it claims to resolve (from
STATE.md). - Build / test output, if the runner produced any.
Verdict — output exactly one
PASS— change is minimal, scoped to the stated item, build/tests green, no out-of-scope edits.REJECT: <one-line reason>— anything below is an automatic reject:- touches files unrelated to the stated item
- build or tests not green (or not run)
- deletes code the task didn't ask to delete
- introduces a secret, broadens permissions, or weakens a check
- larger than "small and self-contained"
Principles
- Default to REJECT when unsure. A rejected fix costs nothing; a bad merge costs trust.
- You are independent of the maker. Do not rationalize its choices.
- One concern at a time — report the first blocking reason, not a wishlist.
Output discipline
Output only PASS or REJECT: <reason>. Nothing else.
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 · 37 lines · 37 tokens per session scan A 68ce21781560
loop-verifier is a skill published in the GitHub repository SUDARSHANCHAUDHARI/MyLoop (2 stars, last pushed 10d ago), licensed MIT. It adds 37 tokens to every session and 360 once invoked, about $0.0002 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-31.
Other skills, from other repositories
fleetq-connect
Connect an agent to FleetQ over MCP or the REST API, including obtaining credentials via dynamic client registration.
fleetq-manage-workflow
Build, validate, cost, and execute FleetQ visual DAG workflows — including generating one from a natural-language goal.
fleetq-run-experiment
Create, run, monitor, and recover a FleetQ experiment through its 20-state pipeline via MCP tools or the REST API.
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
pr-writer
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.