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 boshi-xixixi/TraeSkill --skill audit-integritygit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/audit-integrity)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/audit-integrity"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/audit-integrity.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.1 | $0.00077 | $0.00714 |
| Opus 5 | $0.00039 | $0.00357 |
| Sonnet 5 | $0.00015 | $0.00143 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
audit-integrity 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 7d 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
3 near-identical copies found in the catalogue:
- audit-integrity — 100% identical, 0 lines differ
- audit-integrity — 100% identical, 0 lines differ
- audit-integrity — 95% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Integrity Skill
Enforces output quality, intellectual honesty, and continuous improvement across all AppSec agents.
When to Use
- Every security analysis, code review, threat model, or quality scan agent run
- Applied automatically as a post-analysis quality gate
- Applicable to any agent performing SAST, SCA, threat modeling, or code quality analysis
Components
This skill provides 7 reusable capabilities. Agents apply all 7 unless their scope excludes a specific component.
| Component | Reference File | Purpose |
|---|---|---|
| Clarification Protocol | clarification-protocol.md | Ask ≤2 targeted questions before analysis when scope is ambiguous |
| Anti-Rationalization Guard | anti-rationalization-guard.md | Table of prohibited rationalizations with mandatory responses |
| Self-Critique Loop | self-critique-loop.md | Mandatory second-pass review after initial analysis |
| Retry Protocol | retry-protocol.md | Tool failure handling — retry once, then document |
| Non-Negotiable Behaviors | non-negotiable-behaviors.md | Hard rules: never fabricate, always cite evidence, report gaps |
| Self-Reflection Quality Gate | self-reflection-quality-gate.md | 1–10 scoring rubric with ≥8 threshold per category |
| Self-Learning System | self-learning-system.md | Lesson/Memory templates and governance rules |
Execution Flow
- Before analysis: Apply Clarification Protocol if scope is ambiguous
- During analysis: Apply Anti-Rationalization Guard at every decision point
- After initial pass: Execute Self-Critique Loop (mandatory second pass)
- On tool failure: Apply Retry Protocol
- Before delivery: Run Self-Reflection Quality Gate (all categories must score ≥8)
- After delivery: Create Lessons/Memories for novel findings, false positives, or methodology gaps (see Self-Learning System)
What ships with it
7 files 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.
- references/anti-rationalization-guard.md 3.9 KB
- references/clarification-protocol.md 971 B
- references/non-negotiable-behaviors.md 1.4 KB
- references/retry-protocol.md 560 B
- references/self-critique-loop.md 2.5 KB
- references/self-learning-system.md 2.3 KB
- references/self-reflection-quality-gate.md 2.4 KB
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.
- 7d ago First seen · 51 lines · 77 tokens per session scan A 53b662856bf6
audit-integrity is a skill published in the GitHub repository boshi-xixixi/TraeSkill (261 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 714 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-30.
Other skills, from other repositories
<skill-name>
A template for defining a coding-agent skill, including its title, trigger situations, overview, workflow, common mistakes, and optional references.
spec-writing
A method for writing a software specification: a document that records decisions, reasons, boundaries, and ways to judge whether implementation succeeded. It first checks whether important unknowns require user clarification or technical research.
onboarding-unknown-codebase
A method for quickly understanding an unfamiliar codebase, meaning a software project whose structure and behavior you do not yet know. It builds a project map by examining overview files, directories, and one main execution path.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
clarifying-questions
Guidance for clarifying vague or assumption-heavy requests before making changes.
debugging
A systematic method for finding the underlying cause of a software bug by observing the failure, forming a hypothesis, and testing it.