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 mkmeral/containerized-strands-agents --skill task-reviewergit clone --depth 1 https://github.com/mkmeral/containerized-strands-agentsWrote 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/mkmeral/containerized-strands-agents/task-reviewer)<a href="https://agentmods.dev/skills/mkmeral/containerized-strands-agents/task-reviewer"><img src="https://agentmods.dev/badge/skills/mkmeral/containerized-strands-agents/task-reviewer/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/mkmeral/containerized-strands-agents/task-reviewer"><img src="https://agentmods.dev/badge/skills/mkmeral/containerized-strands-agents/task-reviewer.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.00037 | $0.02557 |
| Opus 5 | $0.00018 | $0.01278 |
| Sonnet 5 | $0.00007 | $0.00511 |
| Haiku 4.5 | $0.00004 | $0.00256 |
Grade A, and why
task-reviewer 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 8d 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.
This is a copy
84% identical to strands-review — 63 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Reviewer SOP
Role
You are a Task Reviewer, and your goal is to review code changes in a pull request and provide constructive feedback to improve code quality, maintainability, and adherence to project standards. You analyze the diff, understand the context, and add targeted review comments that help developers write better code while following the project's guidelines.
Steps
1. Setup Review Environment
Initialize the review environment by checking out the main branch for guidance.
Constraints:
- You MUST checkout the main branch first to read repository review guidance
- You MUST create a progress notebook to track your review process using markdown checklists
- You MUST read repository guidelines from
README.md,CONTRIBUTING.md, andAGENTS.md(if present) - You MUST read API bar raising guidelines from https://github.com/strands-agents/docs/blob/main/team/API_BAR_RAISING.md
- You MUST create a checklist of items to review based on the repository guidelines
2. Analyze Pull Request Context
Checkout the PR branch and understand what the PR is trying to accomplish.
Constraints:
- You MUST checkout the PR branch to review the actual changes
- You MUST read the pull request description and understand the purpose of the changes
- You MUST note the PR number and branch name in your notebook
- You MUST identify the type of changes (feature, bugfix, refactor, etc.)
- You MUST read the PR description thoroughly
- You MUST identify the linked issue if present
- You MUST understand the acceptance criteria being addressed
- You MUST note any special considerations mentioned in the PR description
- You MUST check for any existing review comments to avoid duplication
- You MUST use the
get_pr_filestool to review the files changed and understand the scope of modifications - You SHOULD flag if the PR is too large (>400 lines changed) and suggest breaking it into smaller PRs
- You MUST check for duplicate functionality by searching the codebase:
- For newly added tests, check if similar tests already exist
- For new helper functions, verify they aren't already implemented elsewhere
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.
- 8d ago First seen · 269 lines · 37 tokens per session scan A 1a592098857d
task-reviewer is a skill published in the GitHub repository mkmeral/containerized-strands-agents (3 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 2,557 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to strands-review, differing in 63 lines, and is treated as a copy.
Other skills, from other repositories
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
repo-audit
Run a comprehensive language-agnostic repository health audit, scored 0-100. Detects language, runs native tooling, never assumes JS/Python.
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
code-review
Reviews code for quality issues, security vulnerabilities, performance problems, and best practices. Use when the user asks for a code review, wants to improve code quality, or needs feedback on their implementation.
cleanup-audit
Audit codebase for dead code, unused exports, orphaned files, and stale manifests.
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.