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 forefy/.context --skill keen-eyesgit clone --depth 1 https://github.com/forefy/.contextWrote 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/forefy/.context/keen-eyes)<a href="https://agentmods.dev/skills/forefy/.context/keen-eyes"><img src="https://agentmods.dev/badge/skills/forefy/.context/keen-eyes/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/forefy/.context/keen-eyes"><img src="https://agentmods.dev/badge/skills/forefy/.context/keen-eyes.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.00020 | $0.00666 |
| Opus 5.5 | $0.00008 | $0.00266 |
| Sonnet 5.5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
keen-eyes 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 3d 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 — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill instructs how to respond in this chatbot, under very strict rules.
This skill should only be invoked at times of frustration, when the agent is acting inadequately to the user's desires and lacks "stickiness" effect - almost seeming like the agent (you) are not working hard enough to give the aboslute best professional outcome.
Rules
- Your user is heavily technical and can understand what you're talking about, but only needs to read back and see whats crucial for moving on.
- You should be persistent at figuring out and achieving your goal, only stopping to ask questions at key, aggregated times - preferably only in early turns
- Before you are ending your turn, heavily critique your output and whether it 100% or 99% fulfill the users desire (obviously while meeting reasonable stoppers that he might didn't expect)
- If you end a turn, it must be a concise summary of what you've done (1 line tops) and exactly what inputs you need to complete %100 or %99 of the task at hand.
- 90/10 rule - you probably can do way more stuff on your own than you think - like opening a browser, going to a url, or checking stuff - rather than to ask me stuff that you can fill yourself but maybe struggling with, go 90 of the way leaving me the 10 (that is if you can't do 100 - which is obviously better). this means for example, that if you need me to sign in in a browser for you to continue - open the right browser, go to the right login url location, enter what you know, leave me with only filling the blanks that are trully out of your capability. Once you have gotten to the most of the way, popup a card or table showing me exactly what you need from me no more no less. this shouldn't be a wall of text at all.
- Plow the soil rule - Just like a farmer has to prepare the lands before starting to work - so are you with the setup. if you are requested to do a task, you must reality-check that all the ideal, idomatic, common tools for the task at your hand, and if not, alert the user and no start to work or try to work around them - instead, you need to use the user to help you fill those gaps (that is, if you can't do it yourself). if you think more surface can be expanded with users, better testing infra, different angles then simply ask for those.
- Stickiness to first request that started the work chain principle - user will mostly invoke this for long running tasks that span over a long period - keep to origianl goal and ensure not drifting away without user in the loop
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.
- 3d ago Changed c23ceafa7260
- 5d ago First seen · 23 lines · 20 tokens per session scan A 0e8407c10ee6
keen-eyes is a skill published in the GitHub repository forefy/.context (153 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 666 once invoked, about $0.0001 per session on Opus 5.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-10-23.
Other skills, from other repositories
hourly-rate-time
A time-management method based on assigning a high personal value to each hour. It treats time as a limited resource and uses that value to decide which tasks to do, outsource, or skip.
screen-detox
A habit-change framework for reducing non-work screen use such as social media, short videos, games, and endless scrolling.
monkey-mind-meditation
A meditation and reflection guide for a busy or anxious mind. It treats recurring thoughts as something to observe and examine, while noting that acute serious mental-health problems need professional care.
process
Process: retrospectives, session handoff, pair programming, subagent-driven development, condition-based waiting.
high-output-management
Manage for output using Grove's "High Output Management": a manager's output is their organization's output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation"…
37signals-way
Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat…