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 bartoszarendt/agenticloop --skill review-and-acceptgit clone --depth 1 https://github.com/bartoszarendt/agenticloopWrote 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/bartoszarendt/agenticloop/review-and-accept)<a href="https://agentmods.dev/skills/bartoszarendt/agenticloop/review-and-accept"><img src="https://agentmods.dev/badge/skills/bartoszarendt/agenticloop/review-and-accept/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/bartoszarendt/agenticloop/review-and-accept"><img src="https://agentmods.dev/badge/skills/bartoszarendt/agenticloop/review-and-accept.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.00066 | $0.11483 |
| Opus 5 | $0.00033 | $0.05742 |
| Sonnet 5 | $0.00013 | $0.02297 |
| Haiku 4.5 | $0.00007 | $0.01148 |
Grade A, and why
review-and-accept 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.
How it starts
The opening of the file, as written. The whole thing — 985 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review and accept
The maintainer reviews the implementation artifact against the task record.
For GitHub-backed review, accept only the successful read-only
github-review-prepare exact-head packet as the delegation input. Do not begin
semantic review after failed preparation, and do not repair Engineer evidence,
checkpoint routing, or task contract defects inside a review response. A changed
head invalidates the packet.
## Revision Resolution is a current packet, not a history mirror: it contains
exactly the prior valid needs_revision IDs. For resolved, bind the
structured current-artifact reference (commit:<full-sha> on GitHub); prose
explains the repair without duplicating identity. A prose-only exact current
citation is migration-only; a present stale or malformed reference never falls
back to prose.
Recording the review outcome
Review has exactly two outcomes, and every recorded outcome carries its
provenance (review_mode):
AGENT_REVIEW_STATUS: accepted
AGENT_REVIEW_MODE: host_subagent
AGENT_REVIEW_ARTIFACT: a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0
[[agent: maintainer]]
AGENT_REVIEW_STATUS: needs_revision
AGENT_REVIEW_MODE: host_subagent
AGENT_REVIEW_ARTIFACT: a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0
AGENT_REVIEW_FINDINGS: F-1
[[agent: maintainer]]
review_mode records how the current artifact revision was reviewed. It is
required whenever a review outcome is recorded. reviewed_artifact is required
for files-backed work and must exactly equal implementation_artifact; GitHub
uses the full current PR head in AGENT_REVIEW_ARTIFACT. Valid modes are:
host_subagent– a separate host subagent performed the review;explicit_agent_invocation– a separately invoked review agent;single_agent_fallback– same-session review by the acting agent;independent_human– a human review or confirmation with an explicit reference.
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 Changed · +4 lines ae39c2f3bb38
- 8d ago First seen · 981 lines · 66 tokens per session scan A bd15720ce314
review-and-accept is a skill published in the GitHub repository bartoszarendt/agenticloop (2 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 11,483 once invoked, about $0.0003 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
assignment-review
A review skill for checking submitted Python, Go, code explanations, debugging notes, or practice exercises.
code-review
Comprehensive code review for security, performance, and best practices.
ppt-generation
Use this skill when the user requests to generate, create, or make presentations (PPT/PPTX). Creates visually rich slides by generating images for each slide and composing them into a PowerPoint file.
academic-paper-review
Use this skill when the user requests to review, analyze, critique, or summarize academic papers, research articles, preprints, or scientific publications. Supports comprehensive structured reviews covering methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation.…
code-documentation
Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests…
newsletter-generation
Use this skill when the user requests to generate, create, write, or draft a newsletter, email digest, weekly roundup, industry briefing, or curated content summary. Supports topic-based research, content curation from multiple sources, and professional formatting for email or web distribution. Trigger on requests…