Borrowing it
Nothing to install: this file belongs to hightemp/go_computer_use_mcp_server. 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/hightemp/go_computer_use_mcp_server/main/.codex/skills/aif-best-practices/SKILL.mdgit clone --depth 1 https://github.com/hightemp/go_computer_use_mcp_serverWrote 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/hightemp/go_computer_use_mcp_server/aif-best-practices)<a href="https://agentmods.dev/skills/hightemp/go_computer_use_mcp_server/aif-best-practices"><img src="https://agentmods.dev/badge/skills/hightemp/go_computer_use_mcp_server/aif-best-practices/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/hightemp/go_computer_use_mcp_server/aif-best-practices"><img src="https://agentmods.dev/badge/skills/hightemp/go_computer_use_mcp_server/aif-best-practices.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.00064 | $0.01768 |
| Opus 5 | $0.00032 | $0.00884 |
| Sonnet 5 | $0.00013 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
aif-best-practices 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 257 lines · 64 tokens per session scan A 59a151b3c98f
aif-best-practices is a skill published in the GitHub repository hightemp/go_computer_use_mcp_server (2 stars, last pushed 3mo ago), with no licence file. It adds 64 tokens to every session and 1,768 once invoked, about $0.0003 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-31.
Other skills, from other repositories
trace-mcp-refactoring
Safe refactoring workflow using trace-mcp — assess risk, find candidates, check impact, and rename symbols across all files without missing import sites or cross-file references.
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
audit-architecture
Audit module coupling, cohesion, hidden dependencies, and design smells. Use when conducting architecture reviews, evaluating design decisions, or identifying structural tech debt.
review-thread
Record review verdicts and run the StateNote review thread on an agent-operation instance — every ReviewRequest verdict is one atomic batch-direct-write that advances status and co-writes a reviewnote explaining why, and findings are corrected by appending notes rather than editing them.
find-bugs
Locate likely bug locations in code.
sumo-qa-planning-qa-rollout
Use when you have a chunk of QA work (a story, a PR, a strategy phase) that needs to be turned into a written plan of bite-sized, independently-executable tasks before any test code is written. Walks scope → file structure → bite-sized tasks → confirm, one section per turn. Produces docs/qa/plans/YYYY-MM-DD- .md ready…