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/sandsower/beislid/review-responsenpx skills add sandsower/beislid --skill review-responsegit clone --depth 1 https://github.com/sandsower/beislidWrote 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/sandsower/beislid/review-response)<a href="https://agentmods.dev/skills/sandsower/beislid/review-response"><img src="https://agentmods.dev/badge/skills/sandsower/beislid/review-response.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.1 | $0.00104 | $0.01632 |
| Opus 5 | $0.00052 | $0.00816 |
| Sonnet 5 | $0.00021 | $0.00326 |
| Haiku 4.5 | $0.00010 | $0.00163 |
Grade A, and why
review-response 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 5d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Response
Address post-submission feedback: PR review threads, PR comments, QA ticket comments, and pasted feedback. When fixes belong in an isolated worktree, preserve that worktree context in the response and cleanup notes. See worktree isolation. Categorize feedback, fix what belongs in scope, draft/print or post replies, run needed gates, and push.
Don't use this for: starting new ticket work, creating PRs, or reviewing someone else's PR. Use kickoff, ready-for-review, or pr-patrol instead.
Project config lives at <repo>/.beislid/workflow.md (typed-key fenced YAML blocks; format reference at workflow-md-format.md). Capabilities are probed lazily on first need per probe-semantics.md. Action-risk decisions follow action-policy-protocol.md. Output prose follows output-templates.md and review-response-templates.md.
If the repo declares custom lifecycle hooks, read ../lifecycle-hooks.md and honor any phase-boundary hooks before and after review-response.
Read workflow.md
Read <repo>/.beislid/workflow.md. If it doesn't exist, hard-fail and stop:
🛑 No
workflow.mdfound in.beislid/. If this is a fresh project, run/setupto create one. If you moved your config, restore it to<repo>/.beislid/workflow.md.
Validate line 1 exactly:
<!-- beislid-workflow: v1 -->
If missing or wrong, hard-fail:
⚠️ This
workflow.mdis<found>but review-response only knowsv1. Update Beislið or downgradeworkflow.mdby hand to v1 syntax. Review-response will not silently mis-parse.
Compute cache identifiers:
repo_hash=$(git rev-list --max-parents=0 HEAD | sort | head -c 12)
workflow_hash=$(git hash-object .beislid/workflow.md)
Try to read ${BEISLID_STATE_DIR:-$HOME/.local/state/beislid}/probes/<repo_hash>.json:
- Missing → empty in-memory probe state; cache state
cold. - Present but
workflow_hashmismatch → empty in-memory probe state; cache statestale. - Present and hash matches → load capability entries; cache state
fresh. Per-cap freshness usesprobe_cache.ttl_hoursfrom workflow.md, default 24.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 113 lines · 104 tokens per session scan A cf084674b091
review-response is a skill published in the GitHub repository sandsower/beislid (10 stars, last pushed 6d ago), licensed MIT. It adds 104 tokens to every session and 1,632 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…