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 nitinbhide/tcaitoolkit --skill agent-auditgit clone --depth 1 https://github.com/nitinbhide/tcaitoolkitWrote 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/nitinbhide/tcaitoolkit/agent-audit)<a href="https://agentmods.dev/skills/nitinbhide/tcaitoolkit/agent-audit"><img src="https://agentmods.dev/badge/skills/nitinbhide/tcaitoolkit/agent-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/nitinbhide/tcaitoolkit/agent-audit"><img src="https://agentmods.dev/badge/skills/nitinbhide/tcaitoolkit/agent-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.00060 | $0.01274 |
| Opus 5.5 | $0.00024 | $0.00510 |
| Sonnet 5.5 | $0.00012 | $0.00255 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
agent-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Audit Skill
This skill evaulates AGENTS.md file at the root of the project for following criteria. Objective is to improve the quality of results fromLLMs, reduce the number of turns in agent loop and reduce the LLM token consumptions
How to Audit the AGENTS.md file
- Audit only the repository-root
AGENTS.mdfile. - If the repository root does not contain an
AGENTS.mdfile, stop immediately and report that the audit could not run because the repository-rootAGENTS.mdis missing. - Use the "evaluation criteria" given below and check each item the list
- Treat a "first-level referenced file" as an explicit repository-relative file path written directly in the repository-root
AGENTS.md. - Check only first-level referenced paths for evaluation. Evaluate files that resolve to existing files and skip directories/folders.
- If a first-level referenced path is unresolved or invalid, record it as a warning only. Do not fail the entire audit because of unresolved or invalid referenced paths.
- Do not infer file paths, search the repository for matching filenames, or follow vague references such as "see design docs" unless a concrete file path is given.
- Stop at first-level references from
AGENTS.md. Do not recurse into files referenced by those files. - Output the report using the fixed format defined below.
Output format
Use the following sections in this exact order.
- Target
- Repository root path.
- Audited file path (must be repository-root
AGENTS.md).
- Preflight
- Repository-root
AGENTS.mdpresent: yes/no. - If no, report hard failure and stop.
- Criteria results
- Report one line per criterion.
- Allowed status values: fulfilled, not-fulfilled, not-applicable.
- Include a short rationale for each status.
- Include the evidence file paths used for evaluation.
- Reference path warnings
- List unresolved or invalid first-level referenced file paths as warnings.
- Explicitly state that these warnings do not cause audit failure.
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.
- 1mo ago First seen · 83 lines · 60 tokens per session scan A 8d19200e703f
agent-audit is a skill published in the GitHub repository nitinbhide/tcaitoolkit (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,274 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.