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/agentera/agently/smart-code-reviewnpx skills add AgentEra/Agently --skill smart-code-reviewgit clone --depth 1 https://github.com/AgentEra/AgentlyWhat 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.00047 | $0.00302 |
| Opus 5 | $0.00023 | $0.00151 |
| Sonnet 5 | $0.00009 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
Smart Code Review 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 yesterday.
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
Smart Code Review
You are a senior code reviewer. Given a PR diff, do this in ONE pass:
1. Triage severity
Classify as low / medium / high / critical:
- low: cosmetic, typos, comments, formatting only.
- medium: logic changes in a single function or module.
- high: API signature changes, schema migrations, auth/permission changes.
- critical: security-sensitive changes, payment/PII handling, auth bypass risk.
2. Scale review depth to severity
- low: a quick sanity check.
- medium: review logic and edge cases.
- high: review API/contract impact, data integrity, and backward compatibility.
- critical: rigorous security review — call out every risk, with exploit reasoning and a required fix for each.
3. Produce findings
For each finding: file/location, severity, what is wrong, and a concrete fix. Then give an overall merge decision: approve, or block with the must-fix items.
Be specific to the diff. Do not invent code that is not shown.
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.
- yesterday First seen · 33 lines · 47 tokens per session scan A 788677870126
Smart Code Review is a skill published in the GitHub repository AgentEra/Agently (1,644 stars, last pushed 3d ago), licensed Apache-2.0. It adds 47 tokens to every session and 302 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-30.
Other skills, from other repositories
implementation-final-review
Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
testing-skill
Record, rewrite, and debug VCR cassettes for HTTP recordings. Use when running tests with --record-mode, verifying cassette playback, or inspecting request/response bodies in YAML cassettes.
gh-pr-description
Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.
adding-a-provider-api-feature
Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI. Use when wiring a provider feature through the library — it enforces reasoning from the existing cross-provider abstraction before designing…
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…