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 inbharatai/claude-skills --skill owasp-checkergit clone --depth 1 https://github.com/inbharatai/claude-skillsWrote 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/inbharatai/claude-skills/owasp-checker)<a href="https://agentmods.dev/skills/inbharatai/claude-skills/owasp-checker"><img src="https://agentmods.dev/badge/skills/inbharatai/claude-skills/owasp-checker/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/inbharatai/claude-skills/owasp-checker"><img src="https://agentmods.dev/badge/skills/inbharatai/claude-skills/owasp-checker.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.00030 | $0.00423 |
| Opus 5 | $0.00015 | $0.00211 |
| Sonnet 5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
owasp-checker 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 9d 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
OWASP Checker
Overview
Check for OWASP Top 10 vulnerabilities — injection, broken auth, XSS, insecure deserialization, and misconfiguration.
When to Use This Skill
Use OWASP Checker when you need to:
- Work with owasp checker tasks in your project or workflow
- Automate owasp checker operations at scale
- Generate production-quality owasp checker output quickly
Instructions
When this skill is active, Claude will:
- Understand the full context of your owasp checker request
- Apply best practices and conventions for Security
- Produce clean, well-structured, production-ready output
- Explain key decisions and offer alternatives where relevant
Examples
Example 1 — Basic Usage
User: Help me get started with owasp checker.
Claude: I'll walk you through the essential steps for owasp checker in your context...
Example 2 — Advanced Usage
User: I need a production-ready owasp checker setup with full error handling.
Claude: Here's a complete, production-hardened owasp checker implementation...
Guidelines
- Always validate inputs before processing
- Follow the conventions of the target platform or language
- Prefer explicit over implicit — clarity beats cleverness
- Include comments for non-obvious logic
- Suggest tests or validation steps where appropriate
Dependencies
Required: none
Platforms
Available on: claude.ai, claude-code, api
Part of the claude-skills collection — 183+ skills for Claude.
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.
- 9d ago First seen · 68 lines · 30 tokens per session scan A c2dadc1cc72a
owasp-checker is a skill published in the GitHub repository inbharatai/claude-skills (33 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 423 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-09-03.
Other skills, from other repositories
human-review
Produce a plain-English review of the files you just edited and gate the changes behind an explicit Approve/Undo choice. Use when the Stop hook from the human-review-skill plugin asks for a review (you'll see a prompt referencing an edit log), OR when the developer's most recent message is "1", "2", "approve", or…
optimize
Automatically refines every user prompt into a structured, actionable version, then immediately executes the optimized prompt. When triggered explicitly with "/optimize {prompt}", "optimize:", or "optimize prompt:", outputs the refined prompt as text instead.
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…
mysql-migration
MySQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning MySQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, charset conversions, data backfills, or any DDL touching production tables. Covers online DDL algorithm selection (INSTANT/INPLACE/COPY)…
redis-cache-strategy
Redis caching strategy designer and reviewer. ALWAYS use when designing, reviewing, or troubleshooting Redis caching layers — cache pattern selection (cache-aside, write-through, write-behind), TTL strategy, cache stampede/penetration/avalanche prevention, hot key handling, cache-DB consistency, distributed locking…
systematic-debugging
Use when debugging, diagnosing, or investigating any bug, test failure, flaky test, race condition, unexpected behavior, build failure, production incident, third-party breakage, root cause analysis, or performance regression before proposing fixes.