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/jacopalas/agentic-ai-palas/security-scannpx skills add Jacopalas/agentic-ai-palas --skill security-scangit clone --depth 1 https://github.com/Jacopalas/agentic-ai-palasWrote 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/jacopalas/agentic-ai-palas/security-scan)<a href="https://agentmods.dev/skills/jacopalas/agentic-ai-palas/security-scan"><img src="https://agentmods.dev/badge/skills/jacopalas/agentic-ai-palas/security-scan.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.1 | $0.00045 | $0.01365 |
| Opus 5 | $0.00023 | $0.00682 |
| Sonnet 5 | $0.00009 | $0.00273 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
security-scan 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 5d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/palas-security:security-scan — Basic Security Scanning
IMPORTANT: Before starting execution, inform the user: "ESTOY EJECUTANDO EL SKILL /palas-security:security-scan"
Scan codebase for common security issues: exposed secrets, vulnerable patterns, and risky configurations.
Usage
/security:security-scan [target]
Arguments:
target(Optional): File or directory to scan. Defaults to current directory.
What Gets Scanned
1. Exposed Secrets
Patterns that indicate leaked credentials:
| Pattern | Examples |
|---|---|
| API Keys | api_key, apikey, api-key |
| Secrets | secret, password, passwd, pwd |
| Tokens | token, auth_token, access_token |
| Private Keys | private_key, -----BEGIN.*PRIVATE KEY----- |
| AWS | AKIA, aws_access_key_id, aws_secret_access_key |
| Database | DATABASE_URL, DB_PASSWORD, connection_string |
2. Dangerous Files
Files that should never be committed:
| File | Risk |
|---|---|
.env |
Environment variables with secrets |
.env.local |
Local environment overrides |
credentials.json |
Service account credentials |
*.pem, *.key |
Private keys |
id_rsa, id_ed25519 |
SSH private keys |
.npmrc with tokens |
npm authentication |
secrets.yaml |
Kubernetes secrets |
3. Risky Code Patterns
| Pattern | Language | Risk |
|---|---|---|
eval() |
JS/Python | Code injection |
exec() |
Python | Command injection |
dangerouslySetInnerHTML |
React | XSS vulnerability |
innerHTML = |
JS | XSS vulnerability |
shell=True |
Python subprocess | Command injection |
| SQL string concatenation | Any | SQL injection |
disable_ssl_verification |
Any | MITM vulnerability |
Behavior
- Scan for secrets: Search for exposed credentials
- Check dangerous files: Look for files that shouldn't exist
- Detect risky patterns: Find vulnerable code patterns
- Check .gitignore: Verify sensitive files are ignored
- Report findings: Summarize issues by severity
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.
- 5d ago First seen · 182 lines · 45 tokens per session scan A 61a423760979
security-scan is a skill published in the GitHub repository Jacopalas/agentic-ai-palas (2 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 1,365 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-31.
Other skills, from other repositories
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
simple
Summarize short user notes into clear action items.
agent-ready-cloudflare
Audit and improve website readiness for AI agents using the Cloudflare "Is It Agent Ready?" scanner (isitagentready.com). Covers scanning via API, interpreting results, generating implementation prompts, and fixing every check. Use when the user mentions "agent ready", "isitagentready", "AI agent scan", "agent…
aidlc-master
Runs the AWS AI-DLC (AI-Driven Development Life Cycle) methodology end to end: an adaptive three-phase workflow (Inception → Construction → Operations) with human approval gates, a full audit trail, and all artifacts in aidlc-docs/. Use when the user says "Using AI-DLC", "AI-DLC", "AIDLC", "aidlc-master", or asks for…
security-specialist
Runs security audits on codebases — full scans, diff reviews, threat models, vulnerability triage, remediation guidance, and finding tracking. Activate when the user says "security scan", "audit this repo", "review this PR for security", "threat model", "triage vulnerabilities", "fix this vuln", or "track findings".
ralph-loop-kiro-specs
Automated iterative agent runner for spec-based development in Kiro. Wraps kiro-cli in a self-correcting bash loop that picks up tasks from a Kiro spec, implements them one at a time, verifies against exit criteria, and accumulates corrections and codebase patterns across iterations. Use this skill when the user…