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 Strategic-Automation/violin --skill misconfiggit clone --depth 1 https://github.com/Strategic-Automation/violinWrote 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/strategic-automation/violin/misconfig)<a href="https://agentmods.dev/skills/strategic-automation/violin/misconfig"><img src="https://agentmods.dev/badge/skills/strategic-automation/violin/misconfig/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/strategic-automation/violin/misconfig"><img src="https://agentmods.dev/badge/skills/strategic-automation/violin/misconfig.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.00387 |
| Opus 5.5 | $0.00005 | $0.00155 |
| Sonnet 5.5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
misconfig 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 1mo 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
Configuration, Deployment, and Observability Testing
On-demand skill for weaknesses that arise from how an application is deployed and operated rather than from its code logic: security misconfiguration, information leakage via obscurity, and observability failures (missing logging, monitoring, and error-handling disclosure). It does not contain injection payloads.
When to Use
- Verbose errors, default credentials, exposed management interfaces, or permissive headers/CORS are observed.
- A finding depends on deployment posture, hidden-but-guessable naming, or missing logging/monitoring.
- Do not use for injection, authz, API protocol, or workflow flaws; route those classes to the appropriate specialist skill.
Playbook Routing
| Class | Playbook |
|---|---|
| Security misconfiguration | playbooks/security-misconfiguration.md |
| Security through obscurity | playbooks/security-through-obscurity.md |
| Observability failures | playbooks/observability-failures.md |
Common Pitfalls
- Separate deployment posture from code defects; a misconfiguration is a configuration fix, not a code fix.
- Preserve the exact header, error body, or default credential as decisive evidence.
- Read the playbook stop conditions before probing management interfaces or default credentials.
Verification Checklist
- Engagement bootstrap and scope validation succeeded.
- The matched playbook alone was loaded and bound to the PTT task.
- Evidence captures the exact misconfigured value or missing control.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 43 lines · 13 tokens per session scan A 5e1f41a2f9f7
misconfig is a skill published in the GitHub repository Strategic-Automation/violin (152 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 387 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
performing-jwt-none-algorithm-attack
Execute and test the JWT none algorithm attack to bypass signature verification by manipulating the alg header field in JSON Web Tokens.
bypassing-authentication-with-forced-browsing
Discovering and accessing unprotected pages, APIs, and administrative interfaces by enumerating URLs and bypassing authentication controls during authorized security assessments.
kali-pentest
Execute authorized penetration testing via Kali Linux CLI tools over SSH or Docker. Covers: information gathering, vulnerability analysis, sniffing & spoofing, web/API testing, exploitation, password attacks, wireless, cloud-native security, RFID/NFC, VoIP/ICS, reverse engineering, forensics, post-exploitation/C2, and…
kali-pentest-zh
A Chinese-language guide for carrying out authorized penetration tests with Kali Linux command-line tools through a local system, SSH, or Docker.
api-security-testing
Security-test a REST, GraphQL, or gRPC API with Strix — autonomous agents that enumerate endpoints from an OpenAPI/GraphQL schema (or by crawling), then actually exploit the API-specific vulnerability classes in the OWASP API Security Top 10 (2023) — broken object-level authorization (BOLA/IDOR), broken object…
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…