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 jeffh/claude-plugins --skill implementgit clone --depth 1 https://github.com/jeffh/claude-pluginsWrote 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/jeffh/claude-plugins/implement)<a href="https://agentmods.dev/skills/jeffh/claude-plugins/implement"><img src="https://agentmods.dev/badge/skills/jeffh/claude-plugins/implement/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/jeffh/claude-plugins/implement"><img src="https://agentmods.dev/badge/skills/jeffh/claude-plugins/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 Excessive Agency · line 37 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- high Excessive Agency · line 57 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Excessive Agency · line 3 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00170 | $0.01352 |
| Opus 5.5 | $0.00068 | $0.00541 |
| Sonnet 5.5 | $0.00034 | $0.00270 |
| Haiku 4.5 | $0.00017 | $0.00135 |
Grade A, and why
implement 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Implement
Delegate an implementation task to a Codex subagent running GPT 6.1 Sol (or another GPT model the user names). The subagent will edit files in the current working directory.
Choosing the model
The -m flag selects the model. Default to gpt-6.1-sol, but honor any specific model the user asks for:
- Use
gpt-6.1-solunless the user names a different model. - If the user specifies a model — e.g. "run gpt-5.6-terra", "use gpt-5.5-codex", "with the
<name>model" — pass that exact string to-minstead. Don't validate or second-guess the name; Codex will error if it's unknown. - If they typed
/codex:implement --model <name> <task>(or-m <name>), strip that flag from the prompt and use<name>as the model.
Choosing the effort
Reasoning effort is set with -c model_reasoning_effort="<level>". Default to high, but honor any level the user asks for:
- Use
highunless the user names a different level. - If the user asks in prose — e.g. "low effort", "medium effort" — substitute that level.
- If they typed
/codex:implement --effort <level> <task>, strip that flag from the prompt and use<level>as the effort.
Everywhere below shows -m gpt-6.1-sol and high effort; substitute the chosen model and effort.
How to invoke
-
Take the user's prompt (either the
argspassed to this skill, or the surrounding request if they said "have Codex do X"). -
Run the Bash tool with:
codex exec \ -m gpt-6.1-sol \ -c model_reasoning_effort="high" \ -s workspace-write \ --skip-git-repo-check \ -C "$PWD" \ "<PROMPT>"-m gpt-6.1-sol— the model; defaultgpt-6.1-sol, or the model the user named (see Choosing the model).-c model_reasoning_effort="high"— reasoning effort; defaulthigh, or the level the user named (see Choosing the effort).-s workspace-write— Codex may write files under the workdir +$TMPDIR; this is the safe default.codex execruns non-interactively with approval modenever(there is no-a/--ask-for-approvalflag), so Codex cannot prompt to escalate — it simply stays within the sandbox. Only switch to--dangerously-bypass-approvals-and-sandboxif the user explicitly asks for autonomous, unsandboxed execution.-C "$PWD"— pin the workspace to Claude's current directory.--skip-git-repo-check— allow running outside a git repo. Drop this if the user's task is git-related.- Always set an explicit Bash
timeout. Implementation runs are slow and the Bash default (120000 ms / 2 min) will kill Codex mid-run. Passtimeout: 600000(10 min — the maximum the Bash tool allows) on everycodex execcall. - If the task is large enough that even 10 minutes may not be enough, run the Bash call with
run_in_background: trueinstead and poll its output rather than blocking — a foreground call cannot exceed the 600000 ms cap.
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 Changed 99f4980bcbb2
- 1mo ago First seen · 79 lines · 170 tokens per session scan A 07b0578d9d65
implement is a skill published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 9d ago), licensed Apache-2.0. It adds 170 tokens to every session and 1,352 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.