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-triagenpx skills add SUDARSHANCHAUDHARI/MyLoop --skill loop-triagegit clone --depth 1 https://github.com/SUDARSHANCHAUDHARI/MyLoopWrote 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/sudarshanchaudhari/myloop/loop-triage)<a href="https://agentmods.dev/skills/sudarshanchaudhari/myloop/loop-triage"><img src="https://agentmods.dev/badge/skills/sudarshanchaudhari/myloop/loop-triage.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.00043 | $0.00460 |
| Opus 5 | $0.00022 | $0.00230 |
| Sonnet 5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
loop-triage 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 3d 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-triage
You are the maker in a maker/checker loop. Your only output this run is a rewritten
STATE.md. You do not edit code. You do not touch git. (Those are L2+ and are gated.)
Inputs the runner gives you
- The current
STATE.md(your memory of prior runs). - Recent CI / workflow runs (last 24h).
- Open issues / PRs.
- Recent commits to the default branch (last 24–48h).
What to produce
Rewrite STATE.md with these sections, in this order:
- High Priority — only items a competent engineer would act on today. For each:
what·why it matters·suggested first step· sizeS/M/L. - Watch — real but not urgent. One line each.
- Noise / Ignore — reviewed and dismissed, so the next run doesn't re-surface them.
- Human-flagged — design decisions, security work, or anything unresolved for 3+ runs.
- Facts for next run — approvals, blockers, status to carry forward.
Also update the header: Last run: <UTC timestamp> and Last level: <level>.
Principles
- Signal over noise. When priority is unclear, default to Watch or Noise.
- Be terse. Brevity serves both the next loop and the human skimming it.
- Prune resolved items — do not let the spine grow unbounded.
- Respect existing team practice. No architecture proposals during triage.
- Carry forward human overrides from the prior
STATE.md— never silently drop them.
Output discipline
Output only the full new contents of STATE.md, nothing else. The runner writes
your output to disk verbatim.
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.
- 3d ago First seen · 43 lines · 43 tokens per session scan A 9849af5c1204
loop-triage is a skill published in the GitHub repository SUDARSHANCHAUDHARI/MyLoop (2 stars, last pushed 11d ago), licensed MIT. It adds 43 tokens to every session and 460 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
pushing-ci-changes
Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.
email-triage
Classify incoming emails into triage categories using content analysis, sender profile memory, and thread detection. Produces a category (URGENT, REPLYNEEDED, FYI, NEWSLETTER, NOTIFICATION, SPAM) with confidence and reasoning.
database-verification
Shell-based database connectivity and integrity checks. Verifies that databases are reachable, schemas match expectations, and data integrity constraints hold.
environment-diagnostics
Environment variable validation and configuration verification. Checks that required variables are set, config files parse correctly, ports are available, and system dependencies meet version requirements.
kubernetes
Diagnose and fix Kubernetes pods, services, networking, storage, and rollout failures with kubectl. Safety-first, read-only by default.
gh-ci-analyzer
使用 gh CLI 分析 GitHub Actions CI 日志，提供结构化的故障诊断和报告.