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 jackfranklin/dotfiles --skill review-focus-areasgit clone --depth 1 https://github.com/jackfranklin/dotfilesWrote 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/jackfranklin/dotfiles/review-focus-areas)<a href="https://agentmods.dev/skills/jackfranklin/dotfiles/review-focus-areas"><img src="https://agentmods.dev/badge/skills/jackfranklin/dotfiles/review-focus-areas/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/jackfranklin/dotfiles/review-focus-areas"><img src="https://agentmods.dev/badge/skills/jackfranklin/dotfiles/review-focus-areas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 12 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00027 | $0.00545 |
| Opus 5 | $0.00014 | $0.00272 |
| Sonnet 5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
review-focus-areas 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 9d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Focus Areas Skill
Use this skill when you have completed an implementation and want to prepare a guided review for the user. This skill generates a structured report flagging high-value review points while filtering out menial or uncontroversial changes.
Steps
-
Collect Context:
- Determine the target branch (e.g.
origin/main,master, orHEAD~1if on a single-commit branch). - Generate the diff:
git diff <target-branch>...HEADor similar. - Retrieve the original implementation plan, goals, or requirements from the conversation transcript or active task context.
- Determine the target branch (e.g.
-
Invoke Subagent:
- Invoke the
selfsubagent with the roleFresh Eyes Reviewerto analyze the changes independently. - Provide the subagent with the git diff and the original plan.
- Prompt the subagent to identify:
- Plan Deviations / Hiccups: Where the implementation deviated from the plan, or where unexpected technical hurdles were encountered.
- Risky Changes: Complex logic, state management, potential concurrency/race conditions, error handling gaps, or resource lifecycle issues.
- Uncertainties: Areas where a second opinion or human validation is needed.
- Other Key Areas: Anything else that warrants close human attention.
- Explicitly instruct the subagent to exclude menial changes (imports, formatting, simple renames, boilerplate).
- Invoke the
-
Format Output:
- The subagent should structure the output as a Markdown list of focus areas.
- For each focus area:
- File: Path to the file, formatted as a clickable link (e.g.
[filename](file:///absolute/path/to/file#L123-L145)). - Type: One of
Deviation,Risk,Uncertainty, orAttention. - Explanation: Concise explanation of the change, the reasoning behind it, and why it is flagged.
- Code Snippet: Fenced code block showing the relevant changed or added code.
- File: Path to the file, formatted as a clickable link (e.g.
-
Write Artifact:
- Save the formatted output to a new markdown artifact file named
review_focus_areas.mdin the conversation artifact directory (<appDataDir>/brain/<conversation-id>/). - Present a link to this artifact to the user, highlighting key open questions or decisions.
- Save the formatted output to a new markdown artifact file named
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.
- 9d ago First seen · 38 lines · 27 tokens per session scan A 445908a3df3d
review-focus-areas is a skill published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 545 once invoked, about $0.0001 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…