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/f/check-ai/create-auditnpx skills add f/check-ai --skill create-auditgit clone --depth 1 https://github.com/f/check-aiWhat 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.00066 | $0.01182 |
| Opus 5 | $0.00033 | $0.00591 |
| Sonnet 5 | $0.00013 | $0.00236 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
create-audit 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 yesterday.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Audit
Create new audit modules for the check-ai AI-readiness scanner. Each audit is a single .mjs file in src/audits/ that is dynamically loaded at scan time — no changes to scanner, scorer, or reporter needed.
Audit File Contract
Every audit file must export:
export const section = 'Section Name'; // shown in report
export const checks = [ ... ]; // array of check objects
// optional:
export function analyze(rootDir, ctx) { return { 'custom-key': { found, detail } }; }
The scanner auto-discovers all .mjs files in src/audits/, sorted alphabetically.
Check Object Schema
{
id: 'unique-kebab-id', // unique across all audits
label: 'Display label', // shown in terminal output
section, // use the exported section constant
weight: 5, // 1-20, impact on score
paths: ['file.md', '.dir/'], // candidate paths to probe
type: 'file', // see Check Types below
description: 'Why this matters for AI-readiness',
}
Check Types
| Type | Behavior |
|---|---|
file |
Exists as a file at any of paths |
dir |
Exists as a directory at any of paths |
any |
Exists as either file or directory |
deep-scan |
Walks the file tree for deepPattern matches (requires deepPattern field) |
custom |
Handled by the audit's analyze() function (requires custom field matching a key in analyze's return) |
Weight Guidelines
| Weight | Meaning |
|---|---|
| 1-2 | Nice to have |
| 3-4 | Useful signal |
| 5-7 | Important |
| 8-10 | High impact |
| 15-20 | Critical (use sparingly) |
What ships with it
1 file 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.
- yesterday First seen · 144 lines · 66 tokens per session scan A c1854d368a90
create-audit is a skill published in the GitHub repository f/check-ai (67 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 1,182 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
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
haiku
When writing a haiku for this bot, follow these conventions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.