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 Open-Agent-Tools/General-OAT-Skills --skill checkgit clone --depth 1 https://github.com/Open-Agent-Tools/General-OAT-SkillsWrote 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/open-agent-tools/general-oat-skills/check)<a href="https://agentmods.dev/skills/open-agent-tools/general-oat-skills/check"><img src="https://agentmods.dev/badge/skills/open-agent-tools/general-oat-skills/check.svg" alt="Measured on agentmods" 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.00046 | $0.00242 |
| Opus 5 | $0.00023 | $0.00121 |
| Sonnet 5 | $0.00009 | $0.00048 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
check 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.
What it actually says
Perform a quick status check:
Output Format: Use clear section headers and timestamps for each check.
Tool Validation: First verify that required tools are installed (git, gh, uv) and the project is in a valid git repository.
- Git and workflow status (parallel): Execute
git status,git log --oneline -3, andgh run list --limit=3in parallel to check current state - Package status: Check if package builds successfully with
uv build
Error Handling: If any command fails, attempt to diagnose and fix the issue. If unable to fix, report the specific error and suggest potential solutions.
Provide a concise summary of the project's current state.
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 · 29 lines · 46 tokens per session scan A 01a1aee70d70
check is a skill published in the GitHub repository Open-Agent-Tools/General-OAT-Skills (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 242 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-31.
Other skills, from other repositories
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
planner
Interactive planning and execution for complex tasks. Use when breaking down multi-step projects (planning) or executing approved plans through delegation (execution). Planning creates milestones with specifications; execution delegates to specialized agents. Use when you say "plan this feature", "create…
execution-plans
Manage execution plans as versioned artifacts with progress tracking and decision logs. Use when you say "create execution plan", "update plan progress", "log decision", "complete plan", or "abandon plan". Do NOT use to break work into milestones or delegate tasks (use planner).
work-operating-model
Run a 5-layer interview to elicit how a team actually works (rhythms, decisions, dependencies, institutional knowledge, friction) and emit a structured operating model. Use when you say "elicit operating model", "interview team operating model", "how does this team actually work", or "validate operating model". Do NOT…
ai-agents-docs-of-record
Runbook for this repo's documents of record. Session logs, ADRs, retrospectives, Serena memories, per-issue handoffs, plus the templates, validators, naming rules, and house prose style that bind them. Use when you say write the session log, create an ADR, fill the retro, save this to memory, which document of record.…
omc-ado-triage
Azure DevOps work item triage — surfaces untriaged items, active work, open PRs, pipeline failures, and security alerts. WHEN: User wants to check ADO board status, triage work items, see pipeline health, review open PRs, or get a project health overview. DO NOT USE FOR: Sprint planning (use omc-ado-sprint), PR code…