Borrowing it
Nothing to install: this file belongs to iabhisekbosepm/codex-god-setup. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/iabhisekbosepm/codex-god-setup/main/.agents/skills/audit/SKILL.mdgit clone --depth 1 https://github.com/iabhisekbosepm/codex-god-setupWrote 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/iabhisekbosepm/codex-god-setup/audit)<a href="https://agentmods.dev/skills/iabhisekbosepm/codex-god-setup/audit"><img src="https://agentmods.dev/badge/skills/iabhisekbosepm/codex-god-setup/audit/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/iabhisekbosepm/codex-god-setup/audit"><img src="https://agentmods.dev/badge/skills/iabhisekbosepm/codex-god-setup/audit.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.00024 | $0.00222 |
| Opus 5 | $0.00012 | $0.00111 |
| Sonnet 5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
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 9d 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 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.
- 9d ago First seen · 20 lines · 24 tokens per session scan A 0d7e7b12827e
audit is a skill published in the GitHub repository iabhisekbosepm/codex-god-setup (1 stars, last pushed 5mo ago), with no licence file. It adds 24 tokens to every session and 222 once invoked, about $0.0001 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
auto-test-code
A structured process for critically reviewing and testing software code. It records review findings, test plans, commands, results, and supporting files in a project workspace.
git-pr-review
A read-only reviewer for GitHub pull requests, which are proposed code changes submitted for review. It produces an evidence-based report about whether a pull request should be merged.
code-reviewer
A code-review workflow that checks completed work against its requirements or plan before merging. It groups findings by severity and gives each issue a fix and a way to verify it.
improve-codebase-architecture
Find architecture deepening, terminology, and semantic-symmetry opportunities in a codebase. Use for architecture or refactoring audits, tightly coupled or shallow modules, weak test seams, scattered domain concepts, overloaded names, or sibling workflows whose ownership and transitions drift unexpectedly. Do not use…
change-impact
Map affected consumers and verification obligations before implementing or reviewing a change that crosses interfaces, persistence or schemas, permissions, deployment or release boundaries, or three or more downstream branches. Use for blast-radius and what-could-break questions. Do not use for ordinary local edits…
causal-explanation
Explain why or how an existing consequential behavior, design choice, regression, threshold, or tradeoff exists from current evidence and relevant history. Use for why, how, rationale, or postmortem questions and to explain an established root cause or regression finding; do not use to reproduce, diagnose, or…