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 nortonx/ai-tooling-free --skill security-checkgit clone --depth 1 https://github.com/nortonx/ai-tooling-freeWrote 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/nortonx/ai-tooling-free/security-check)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/security-check"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/security-check/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/nortonx/ai-tooling-free/security-check"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/security-check.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.00060 | $0.00662 |
| Opus 5.5 | $0.00024 | $0.00265 |
| Sonnet 5.5 | $0.00012 | $0.00132 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
security-check 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments
[<path>]
- Optional. A file or directory to scope the audit; omit to audit the whole project.
- Examples:
/security-check,/security-check src/api
Copilot CLI note:
$ARGUMENTSdoes not substitute in skills; include the argument inline in your prompt.
Security check: $ARGUMENTS
Audit the code against the OWASP Top 10 and report the findings. Read the relevant code (route handlers, authentication, database access, configuration, dependencies) before asserting anything: a finding without evidence in the code is noise and costs the trust of whoever has to fix it.
Language and style
Write the report in the language of the user's request. Use active voice, short sentences, one idea per paragraph, no decorative emoji, and explain why each risk matters, not only what it is. Keep code identifiers in backticks with their original spelling.
OWASP Top 10
- Injection: SQL, NoSQL, OS commands, LDAP, XPath
- Authentication and sessions: weak passwords, insecure credential storage, session fixation, missing session timeout
- XSS: reflected, stored, DOM-based, missing output encoding
- Insecure direct object reference (IDOR): unauthorized access, missing access controls
- Security misconfiguration: insecure defaults, unnecessary features enabled, missing security headers, verbose errors
- Sensitive data exposure: unencrypted data, weak encryption, leaks in logs or URLs
- CSRF: missing or weak CSRF tokens
- Vulnerable dependencies: outdated libraries, missing security patches
- Logging and monitoring: missing audit trails, inadequate error logging
- API security: missing rate limiting, weak authentication, excessive data exposure
Report
For each finding, give these fields:
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 · 63 lines · 60 tokens per session scan A fd48c877c8a3
security-check is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 8d ago), licensed MIT. It adds 60 tokens to every session and 662 once invoked, about $0.0002 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-10-10.
Other skills, from other repositories
api-security-patterns
Skill "api-security-patterns" from frank-luongt/faos-skills-marketplace, covering advanced api security patterns, when to use this skill, how it works, step 1: threat model the api surface and step 2: implement the authentication layer.
multi-agent-patterns
Skill "multi-agent-patterns" from frank-luongt/faos-skills-marketplace, covering multi-agent architecture patterns, when to activate, core concepts, detailed topics and why multi-agent architectures.
app-store-optimization
Skill "app-store-optimization" from frank-luongt/faos-skills-marketplace, covering app store optimization (aso), use this skill when, do not use this skill when, instructions and platform differences: apple vs. google.
campaign-analytics
Skill "campaign-analytics" from frank-luongt/faos-skills-marketplace, covering campaign analytics, use this skill when, do not use this skill when, instructions and multi-touch attribution models.
customer-success-playbook
Skill "customer-success-playbook" from frank-luongt/faos-skills-marketplace, covering customer success playbook, use this skill when, do not use this skill when, instructions and customer lifecycle stages.
enterprise-search
Skill "enterprise-search" from frank-luongt/faos-skills-marketplace, covering enterprise search, use this skill when, do not use this skill when, instructions and search architecture patterns.