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 rhtevan/agentfs --skill agentfs-violation-chkgit clone --depth 1 https://github.com/rhtevan/agentfsWrote 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/rhtevan/agentfs/agentfs-violation-chk)<a href="https://agentmods.dev/skills/rhtevan/agentfs/agentfs-violation-chk"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/agentfs-violation-chk/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/rhtevan/agentfs/agentfs-violation-chk"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/agentfs-violation-chk.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.01727 |
| Opus 5.5 | $0.00010 | $0.00691 |
| Sonnet 5.5 | $0.00005 | $0.00345 |
| Haiku 4.5 | $0.00002 | $0.00173 |
Grade A, and why
agentfs-violation-chk 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 22d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentFS Violation Check
Full behavioral self-audit of session conduct against the agent's
rules (AGENTS.md guardrails) and principles (SOUL.md). Unlike
agentfs-ctx-chk which audits the context files for structural
health, this skill audits the agent's behavior during the current
session for compliance violations.
Use this when you suspect the agent has drifted, after context compaction, or as a periodic integrity check. The lightweight version of this check runs automatically at Session Canary re-verification points (turn 5, then every 10 turns) — this skill is the full, explicit version.
Prerequisites
AGENTS.mdis loaded in context (contains rules to audit against).agents/SOUL.mdis accessible (contains principles to audit against)- Session has ≥2 turns of history to audit
How It Differs from Related Skills
| Skill | Question |
|---|---|
agentfs-violation-chk (this) |
"Did I violate my own rules this session?" |
agentfs-ctx-chk |
"Are the context files well-engineered?" |
agentfs-eval |
"Is this workspace structurally healthy?" |
Specification
| ID | Capability | Verifiable By |
|---|---|---|
| S1 | Audit all AGENTS.md rules against session behavior | Report covers every numbered rule |
| S2 | Audit all SOUL.md principles against session behavior | Report covers every named principle |
| S3 | Identify specific turns where violations occurred | Each finding cites the turn or action |
| S4 | Distinguish severity levels | Findings classified as 🔴 violation, 🟡 borderline, 🟢 clean |
| S5 | Produce actionable remediation | Each violation includes what should have been done |
Steps
Step 1 — Gather Audit Baseline
Read the rules and principles that govern behavior:
- Review the Rules section of
AGENTS.mdcurrently in context. List every numbered rule (e.g., Signal Dispatch, Pre-Flight, Post-Write, Session Canary, Conflict Resolution, Checkpoint, Scope Rules). - Review the Principles section of
.agents/SOUL.mdcurrently in context. List every named principle (e.g., No assumed inputs, Direct communication, Intellectual integrity, etc.).
What ships with it
1 file 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.
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.
- 22d ago First seen · 197 lines · 24 tokens per session scan A f971eda2c241
agentfs-violation-chk is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 1,727 once invoked, about $0.0001 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-09-30.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…