Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tomkrikorian/visionOSAgentsnpx agentmods add skills/tomkrikorian/visionosagents/tkr-skill-writerWrote 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/tomkrikorian/visionosagents/tkr-skill-writer)<a href="https://agentmods.dev/skills/tomkrikorian/visionosagents/tkr-skill-writer"><img src="https://agentmods.dev/badge/skills/tomkrikorian/visionosagents/tkr-skill-writer/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/tomkrikorian/visionosagents/tkr-skill-writer"><img src="https://agentmods.dev/badge/skills/tomkrikorian/visionosagents/tkr-skill-writer.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.00037 | $0.01273 |
| Opus 5 | $0.00018 | $0.00636 |
| Sonnet 5 | $0.00007 | $0.00255 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
tkr-skill-writer 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 10d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TKR Skill Writer
Description and Goals
This skill provides guidelines and templates for creating well-structured skills that follow consistent patterns in this repository while staying aligned with the current Codex skill guide. Skills should be clear, discoverable, and provide actionable guidance for developers.
Goals
- Standardize skill structure across all skills in the repository
- Ensure skills are discoverable and easy to navigate
- Provide clear "when to use" guidance for each skill
- Maintain consistent reference file organization
- Keep repo conventions separate from actual Codex requirements
- Include optional Codex metadata when it improves discovery and presentation
- Enable efficient skill creation and maintenance
What This Skill Should Do
When creating or updating a skill, this skill guides you to:
-
Start from the official minimum:
- A skill folder with a
SKILL.mdfile - Frontmatter with
nameanddescription - Instructions that explain exactly when the skill should trigger
- A skill folder with a
-
Apply this repo's preferred structure:
- Description and Goals
- What This Skill Should Do
- Information About the Skill (with subcategories)
-
Create reference files that are:
- One level deep from SKILL.md (e.g.,
references/filename.md) - Use relative paths from the skill root
- Avoid deeply nested reference chains
- One level deep from SKILL.md (e.g.,
-
Organize component/system references in tables with:
- Component/System name as a clickable link:
[ComponentName](references/componentname.md) - "When to Use" descriptions that clearly explain when to load each reference
- Component/System name as a clickable link:
-
Add optional metadata when useful:
- Create
agents/openai.yamlfor UI metadata in the Codex app - Set
interface.display_name,short_description,icon_small,icon_large, andbrand_color - Add
interface.default_promptonly when a starter prompt will improve skill discoverability or invocation clarity - Add
policyordependenciesonly when the skill genuinely needs them
- Create
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 177 lines · 37 tokens per session scan A d967094167c9
tkr-skill-writer is a skill published in the GitHub repository tomkrikorian/visionOSAgents (61 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,273 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…