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/talont-org/autoskillit/validate-auditnpx skills add TalonT-Org/AutoSkillit --skill validate-auditgit clone --depth 1 https://github.com/TalonT-Org/AutoSkillitWrote 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/talont-org/autoskillit/validate-audit)<a href="https://agentmods.dev/skills/talont-org/autoskillit/validate-audit"><img src="https://agentmods.dev/badge/skills/talont-org/autoskillit/validate-audit.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 | $0.00072 | $0.04808 |
| Opus 5 | $0.00036 | $0.02404 |
| Sonnet 5 | $0.00014 | $0.00962 |
| Haiku 4.5 | $0.00007 | $0.00481 |
Grade A, and why
validate-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 4d 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 — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Audit Findings Skill
Validate audit findings from audit-arch, audit-tests, or audit-cohesion against actual
code, git history, and design intent using 9–10 parallel subagents. Contested findings are
separated into their own file. The validated report carries a validated: true marker to
signal downstream processing.
When to Use
- User says "validate audit", "validate findings", "validate report", "check audit results"
- After running
audit-arch,audit-tests, oraudit-cohesionto filter noise before acting
Arguments
{audit_report_path}
audit_report_path— absolute path to an audit report produced byaudit-arch,audit-tests, oraudit-cohesion. If omitted, use the most recent file under{{AUTOSKILLIT_TEMP}}/audit-arch/,{{AUTOSKILLIT_TEMP}}/audit-tests/, or{{AUTOSKILLIT_TEMP}}/audit-cohesion/(most recent mtime wins across all three). If no files exist under any of these directories, print an error message and exit with a non-zero status.
Critical Constraints
NEVER:
- Modify any source code files
- Create files outside the per-run output directory (
{{AUTOSKILLIT_TEMP}}/validate-audit-{YYYY-MM-DD_HHMMSS}/) - Issue subagent Task calls sequentially — ALL must be in a single parallel message
- Write output files before synthesizing ALL subagent results
- Subagents must NOT create their own files — they return findings in response text only
- Do NOT include VALID BUT EXCEPTION WARRANTED findings in the validated report body — they belong in the validation summary only
ALWAYS:
- Use
model: "sonnet"when spawning all subagents via the Task tool - Issue all Task calls in a single message to maximize parallelism
- Write
validated: trueas the first line of the validated report file - Respect interactive vs headless mode for the approval step (Step 6)
Finding Verdicts
| Verdict | Meaning | Action |
|---|---|---|
| VALID | Finding confirmed by code evidence | Include as-is in validated report |
| VALID BUT EXCEPTION WARRANTED | Real issue; documented constraint applies | Include with exception note |
| CONTESTED | Factually wrong or counterproductive | Exclude from report; write to contested file |
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.
- 4d ago First seen · 483 lines · 72 tokens per session scan A bbe6aa4464cd
validate-audit is a skill published in the GitHub repository TalonT-Org/AutoSkillit (5 stars, last pushed 5d ago), licensed MIT. It adds 72 tokens to every session and 4,808 once invoked, about $0.0004 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
edgeone skill scanner
Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描…
portaljs-check-data-quality
Audit a local or remote tabular file (CSV/TSV) for common data quality issues — schema, nulls, types, duplicates. Read-only. Use when a dataset needs a quality check before publishing, or a showcase renders wrong (blank cells, garbled numbers, an unsortable date column) and the cause needs isolating.
agent-review
Critically review a Stencila agent and suggest improvements. Use when asked to review, audit, critique, evaluate, or improve an agent directory or AGENT.md file. Covers frontmatter validation, system instruction quality, configuration correctness, and adherence to the Agent schema.
Website Audit
Comprehensive website auditing skill using Lighthouse, PageSpeed Insights, and web performance APIs to audit performance, accessibility, SEO, best practices, and security.
aws-security-audit
AWS security auditing — IAM users/roles/policies, CloudTrail API events, security posture analysis. Use when auditing IAM permissions, investigating security incidents, checking MFA compliance, or tracing API activity in CloudTrail.
jentic
Use this skill whenever the user wants to work with a third-party or external API/tool through the Jentic platform — e.g. asks to "find the vessel-tracking API and add it", "get rows from this Google Sheet", connect Slack, import/search/discover an API, integrate or automate a SaaS, pull data from a service, or call…