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 Djtony707/TITAN --skill production-auditgit clone --depth 1 https://github.com/Djtony707/TITANWrote 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/djtony707/titan/production-audit)<a href="https://agentmods.dev/skills/djtony707/titan/production-audit"><img src="https://agentmods.dev/badge/skills/djtony707/titan/production-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/djtony707/titan/production-audit"><img src="https://agentmods.dev/badge/skills/djtony707/titan/production-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.01663 |
| Opus 5 | $0.00020 | $0.00831 |
| Sonnet 5 | $0.00008 | $0.00333 |
| Haiku 4.5 | $0.00004 | $0.00166 |
Grade A, and why
production-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 11d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- production-audit — 100% identical, 0 lines differ
- production-audit — 98% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Audit
Use this skill when the user asks whether an application is ready to ship, what could break in production, or what must be fixed before a launch. This is a maintainer-safe rewrite of the stale community production-audit idea: it keeps the useful production-readiness lens and removes unpinned external execution and third-party data sharing.
When to Use
- The user asks "is this production-ready", "what would break in prod", "what did we miss", "audit this repo", or "ready to ship?"
- A feature was merged and needs a pre-deploy or post-merge risk pass.
- A public launch, demo, customer rollout, or investor walkthrough is close.
- CI is green but the user wants production risk, not only test status.
- A deployed URL, release branch, PR, or current checkout is available for evidence gathering.
When Not to Use
- During active implementation when the right lens is line-level secure coding;
use
security-reviewfirst. - For pure libraries, templates, docs-only repos, or scaffolds unless the user wants packaging/release readiness rather than application readiness.
- When the user asks for a formal compliance audit. This skill is engineering triage, not legal, financial, medical, or regulatory certification.
- When the only available evidence is a product idea with no repo, deployment, CI, or runtime surface.
How It Works
Build the audit from local and user-authorized evidence. Do not run unpinned remote code, upload repository contents to third-party services, or call external scanners unless the user explicitly approves that specific tool and data flow.
Use this order:
- Establish the release surface.
- Read recent changes and current branch state.
- Inspect runtime, auth, data, payment, background-job, AI, and deployment boundaries that actually exist in the repo.
- Check CI, tests, migrations, environment documentation, and rollback path.
- Produce a short ship/block recommendation with specific fixes.
Evidence Checklist
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.
- 11d ago First seen · 207 lines · 41 tokens per session scan A 54f769ac5ad4
production-audit is a skill published in the GitHub repository Djtony707/TITAN (19 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,663 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-30.
Other skills, from other repositories
Phone Use
MUST Load this skill for ANY task that involves GUI interaction or device control — opening apps, tapping, typing, scrolling, swiping, Back/Home/Recents, reading the screen, or any workflow that touches on-screen content. Load this even when the user does not explicitly mention the device — if the task implies a GUI…
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
automation
Instructions for managing scheduled tasks through the host's structured automation tool, including reminders, delayed work, recurring checks, and result delivery.
robust-error-handling-in-scripts
Use this skill when writing shell scripts, Python automation, or any unattended batch job. Ensure failures are detected, logged, and handled — never silently ignored.
structured-logging-and-observability
Use this skill when building production services, pipelines, or automation that needs to be debugged, monitored, or audited. Add structured logs, metrics, and health checks before shipping any service.
rosclaw-embodied
A set of rules for completing robot tasks in ROSClaw, a system for running and checking robot work. It covers approved robot files, acceptance evidence, and separate rules for simulation and real hardware.