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 agentmods add skills/mdlmarkham/tailopsmcp/code-reviewernpx skills add mdlmarkham/TailOpsMCP --skill code-reviewergit clone --depth 1 https://github.com/mdlmarkham/TailOpsMCPWhat 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 | $0.00060 | $0.00959 |
| Opus 5 | $0.00030 | $0.00479 |
| Sonnet 5 | $0.00012 | $0.00192 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
code-reviewer 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 2d 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 ships with it
6 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.
- 2d ago First seen · 210 lines · 60 tokens per session scan A 777841d763d1
code-reviewer is a skill published in the GitHub repository mdlmarkham/TailOpsMCP (16 stars, last pushed 8mo ago), with no licence file. It adds 60 tokens to every session and 959 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-30.
Other skills, from other repositories
fix-issues
Fix a batch of open GitHub issues end to end - one git worktree and one agent per issue (feature-dev for implementation, review-pr for review), individual PRs into develop, a release PR to main with a final multi-agent integration review, and optional tag/release/issue-comment publishing. Use when the user asks to…
file-issue
File a GitHub issue on this repo with the required title prefix and labels. Use when opening an issue, or when a finding during other work is worth tracking rather than fixing inline.
mcp-control-plane-audit
Audit the local MCP control plane, Codex MCP registration, Python MCPServer entrypoints, tool capability inventory, stateless MCP conformance wiring, and project-scoped agent skills. Use for MCP upgrades, configuration security reviews, onboarding MCP servers, verifying Agent Skills, diagnosing missing tools, or…
meal-planning
Plan meals collaboratively in chat, then publish the finalized plan to mealforge via its MCP tools. Use when the user wants to plan meals (a week of dinners, a few breakfasts, a single meal), revise a pushed plan, switch or complete the active plan, or push a plan to mealforge.
feature-development
The required workflow for adding a feature to this monorepo — spec, generator scaffold, failing tests, then implementation. Use whenever adding a new feature, endpoint, screen, or capability. Never create feature directories by hand.
tanstack-router-patterns
Canonical patterns for the web app's TanStack Router + TanStack Query setup — file-based routing, the generated route tree, data fetching, and API client wiring. Use when adding routes, pages, or data fetching in apps/web.