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 notifygit 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/notify)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/notify"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/notify/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/notify"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/notify.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.00034 | $0.00264 |
| Opus 5.5 | $0.00014 | $0.00106 |
| Sonnet 5.5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
notify 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 1mo 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
Notify the parent
Use the notify_user tool to tell the parent something genuinely worth their
attention:
- The child finished a tutoring session or a practice test — with a one-line note on how it went.
- A new study sheet, test, or progress report is ready to review.
- A backup completed, or a remote backup still needs setting up.
- Something needs the parent's decision or sign-off.
Two ways to notify:
- Quick alert → the
notify_usertool (a desktop notification). Keep it a title plus one or two sentences. - Important or detailed (a weekly summary, "a new report is ready", something
to keep) → send an email via the
notify_usertool's email delivery (pass the email fields — recipient, subject, body; inline HTML is fine). Prefer email for substantive updates the parent should read later.
Do NOT notify for trivial or routine steps — only when the parent would truly want to know. Keep every message plain, warm, and non-technical.
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.
- 1mo ago Changed · -1 lines 093b4b64e1ca
- 1mo ago First seen · 28 lines · 34 tokens per session scan A 0ea51a58f9ea
notify is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 20d ago), licensed MIT. It adds 34 tokens to every session and 264 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-08-30.
Other skills, from other repositories
scenario-design
Draft real-life test SCENARIOS (not smoke tests) from a change/feature spec. Derives edge-case, performance, frontend-quirk and error-handling scenarios with ISTQB techniques, routes each to a test level, and writes test-plan.md, emitting clarification questions on a spec gap. Use on "design test scenarios", "what…
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
mockery-suite-tests
Use when writing Go tests that need test doubles or cover multiple cases - detect the repo's mocking approach (Mockery v3, gomock, hand-written testify mocks, fakes), table-driven cases, testify suites when the repo uses them, and real-Postgres tests for repository adapters.
goga-accept-test-assessment
Cell test coverage assessment for acceptance review.
goga-cell-go
Golang rules for implementing CODEMANIFEST contracts.
goga-accept-usage-review
Validate cell-level usage files against actual implementation during acceptance.