Borrowing it
Nothing to install: this file belongs to zkysar1/Claude-Mind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zkysar1/Claude-Mind/main/.claude/skills/fresh-eyes-close/SKILL.mdgit clone --depth 1 https://github.com/zkysar1/Claude-MindWrote 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/zkysar1/claude-mind/fresh-eyes-close)<a href="https://agentmods.dev/skills/zkysar1/claude-mind/fresh-eyes-close"><img src="https://agentmods.dev/badge/skills/zkysar1/claude-mind/fresh-eyes-close/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/zkysar1/claude-mind/fresh-eyes-close"><img src="https://agentmods.dev/badge/skills/zkysar1/claude-mind/fresh-eyes-close.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00208 | $0.02587 |
| Opus 5 | $0.00104 | $0.01293 |
| Sonnet 5 | $0.00042 | $0.00517 |
| Haiku 4.5 | $0.00021 | $0.00259 |
Grade A, and why
fresh-eyes-close 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.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fresh-eyes-close — Independent Blocking Close Review
Produces the verdict artifact the close-review gate reads. The gate
(close-review-gate.py, g-357-40) refuses a tier-2 close without an APPROVE
verdict; this skill is what writes one — or, more often and more usefully,
what writes the REJECT that sends the work back.
The one rule that makes this skill worth having
The reviewer MUST NOT be the closing agent. The gate enforces it
(independence_defect refuses an APPROVING verdict whose reviewer is the
closer, and refuses one that names no reviewer at all; a REJECT on your own
close is allowed — finding fault in your own work needs no independence, and
refusing it would suppress the record rather than the conflict), and the verdict path is
goal-keyed and world-scoped precisely so an independent party can write it.
Independence order, per coordination.md Review Gate:
- A live peer agent via the review-request lane — check with
bash core/scripts/liveness-check.sh --agent <peer> --jsonand conclude a peer is unavailable only ondormant(never onunknown). - A fresh-context subagent when no peer is live. Always available, and the fallback solo deployments depend on.
A fresh-context reviewer is not a weaker substitute for the whole defect class this gate exists for: the founding incident (coach g-012-02) was refutable from the goal description alone. A peer additionally catches shared-prior blind spots, which is why it is preferred where one exists.
What the reviewer receives — and what it must NOT
Give the reviewer ONLY:
- the goal record: title, description, verification criteria, and any referenced source message ids resolved to their text
- the artifact paths
- the adversarial mandate below
Never hand over the executing session's context, reasoning, or narrative. The review is worth exactly what its independence is worth, and a reviewer primed with the author's account of why the work is correct is no longer independent.
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 · 211 lines · 208 tokens per session scan A 5d77eacbf67a
fresh-eyes-close is a skill published in the GitHub repository zkysar1/Claude-Mind (5 stars, last pushed 3d ago), licensed MIT. It adds 208 tokens to every session and 2,587 once invoked, about $0.0010 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-09-03.
Other skills, from other repositories
code-review
Perform structured code reviews with actionable feedback. Use when a user asks to review code, check code quality, find bugs, audit security, improve performance, or assess maintainability. Trigger when user says things like "review this code", "check for bugs", "is this code secure", "any issues with this", "code…
code-review
A tool for reviewing changes in a Git repository. Git is a system that records code changes, and a diff shows exactly what was added, removed, or edited.
ast-analyzer
Deep Abstract Syntax Tree analysis for understanding code structure, dependencies, impact analysis, and pattern detection at the structural level across multiple programming languages.
quality-standards
Defines code quality benchmarks, standards compliance, and best practices for maintaining high-quality codebases.
security-audit
Security audit expert for OWASP Top 10, CVE analysis, code review, and penetration testing methodology.
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.