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/aurite-ai/agent-verifier/verify-patternsnpx skills add Aurite-ai/agent-verifier --skill verify-patternsgit clone --depth 1 https://github.com/Aurite-ai/agent-verifierWrote 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/aurite-ai/agent-verifier/verify-patterns)<a href="https://agentmods.dev/skills/aurite-ai/agent-verifier/verify-patterns"><img src="https://agentmods.dev/badge/skills/aurite-ai/agent-verifier/verify-patterns.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.00049 | $0.03021 |
| Opus 5 | $0.00024 | $0.01510 |
| Sonnet 5 | $0.00010 | $0.00604 |
| Haiku 4.5 | $0.00005 | $0.00302 |
Grade A, and why
verify-patterns 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 3d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Pattern Verification
Purpose
Verify AI agent code for common anti-patterns that can cause infinite loops, runaway retries, tool mismatches, and context overflow. All analysis happens locally.
When to Use
Trigger this skill when the user asks to:
- "verify agent patterns"
- "check agent loops"
- "verify tools"
- "check retry limits"
- "verify agent safety"
Note: For full verification including security, quality, and language-specific checks, tell the user to say "verify agent".
Process
Step 1: Detect Agent Framework
Identify the agent framework by checking imports in Python/TypeScript files:
| Import Pattern | Framework |
|---|---|
from langgraph or import langgraph |
LangGraph |
from crewai or import crewai |
CrewAI |
from autogen or import autogen |
AutoGen |
from langchain or import langchain |
LangChain |
Direct openai/anthropic SDK only |
Custom |
Also check for framework config files: langgraph.json, crew.yaml.
Step 2: Locate Agent Files
Find files to analyze:
Priority files:
graph.py,graph.ts- Agent workflow definitionstools.py,tools.ts,tools/*.py,tools/*.ts- Tool implementationsstate.py,state.ts- State schemasprompts.py,prompts/*.md,system.md- Prompt templatesagent.py,agent.ts- Main agent logic
Directories to check:
src/agent/,agent/,src/, project rootlib/,app/,packages/
Exclude from analysis:
skills/directory — these are skill definitions, not agent system prompts
Step 3: Run Pattern Checks
Check Tiers
[PATTERN]— Mechanical check. Apply exactly as written.[HEURISTIC]— Judgment required. Mark findings clearly.
Tag every finding with [P] for pattern or [H] for heuristic.
3.1 [PATTERN] Loop Safety
Apply mechanically. Do not pass a loop because it "looks like it might terminate."
| Pattern to find | Pass condition | Severity |
|---|---|---|
while True: in Python |
A break statement exists within the same block scope |
⚠️ Warning if absent |
for { } in Go |
A break or return exists within the block |
⚠️ Warning if absent |
while (true) in TS/JS |
A break or return exists within the block |
⚠️ Warning if absent |
| Function calls itself recursively | A non-recursive return path exists (base case), OR a depth/counter parameter is present | ⚠️ Warning if absent |
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.
- 3d ago First seen · 348 lines · 49 tokens per session scan A ac539800d3fa
verify-patterns is a skill published in the GitHub repository Aurite-ai/agent-verifier (44 stars, last pushed 7d ago), licensed MIT. It adds 49 tokens to every session and 3,021 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
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
Tech Debt Auditor
Identifies and prioritizes technical debt in a codebase with an effort/impact matrix.
Unit Test Improver
Reviews existing unit tests for gaps, weak assertions, and missing edge cases, then rewrites them to be more robust.
Refactor Planner
Creates a safe, step-by-step plan to refactor messy code without breaking existing behavior.
observability
This skill should be used when the user asks about "observability", "logging", "metrics", "tracing", "monitoring", "structured logging", "log format", "log levels", "distributed tracing", "OpenTelemetry", "health checks", or needs guidance on implementing observability and monitoring requirements.
setup
This skill should be used when the user asks about "project setup", "project initialization", "repository setup", "new project", "bootstrap project", "project structure", "development environment", "toolchain setup", "project configuration", or needs guidance on setting up new projects that comply with SDLC standards.