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 agents/pdugan20/claudelint/agent-toolsgit clone --depth 1 https://github.com/pdugan20/claudelintWrote 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/agents/pdugan20/claudelint/agent-tools)<a href="https://agentmods.dev/agents/pdugan20/claudelint/agent-tools"><img src="https://agentmods.dev/badge/agents/pdugan20/claudelint/agent-tools.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.00017 | $0.00484 |
| Opus 5 | $0.00009 | $0.00242 |
| Sonnet 5 | $0.00003 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
agent-tools 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.
What it actually says
agent-tools
Rule Details
This rule enforces two constraints on the tools field in agent markdown frontmatter. First, tools must be a valid array of strings representing tool names the agent is allowed to use. Second, tools and disallowedTools are mutually exclusive -- specifying both is an error. Array validation is delegated to AgentFrontmatterSchema.shape.tools, while cross-field validation uses AgentFrontmatterWithRefinements. This prevents conflicting tool access configurations.
Incorrect
Tools as a single string instead of array
---
name: code-agent
description: Writes and edits code
tools: Bash
---
Both tools and disallowedTools specified
---
name: code-agent
description: Writes and edits code
tools:
- Bash
- Edit
disallowedTools:
- Write
---
Correct
Tools as a valid array of tool names
---
name: code-agent
description: Writes and edits code
tools:
- Bash
- Edit
- Read
---
Using disallowedTools alone (without tools)
---
name: safe-agent
description: Agent with restricted access
disallowedTools:
- Bash
---
How To Fix
Ensure tools is a YAML array of strings. If you need to restrict certain tools, use either tools (allowlist) or disallowedTools (blocklist), but not both.
Options
This rule does not have any configuration options.
Related Rules
Resources
Version
Available since: v0.2.0
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 · 85 lines · 17 tokens per session scan A d94ce95b20dc
agent-tools is an agent published in the GitHub repository pdugan20/claudelint (11 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 484 once invoked, about $0.0001 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 agents, from other repositories
nodejs-expert
Use this agent when you need expert Node.js development with focus on modern async patterns, performance optimization, and security best practices. This agent specializes in Node.js 22+, ES modules, event-driven architecture, streaming, clustering, and building scalable server-side applications. Examples: Context…
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
AGENTS
Every persona file MUST begin with a YAML frontmatter block.