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 identity-authgit 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/identity-auth)<a href="https://agentmods.dev/skills/strategic-automation/violin/identity-auth"><img src="https://agentmods.dev/badge/skills/strategic-automation/violin/identity-auth/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/identity-auth"><img src="https://agentmods.dev/badge/skills/strategic-automation/violin/identity-auth.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.00417 |
| Opus 5 | $0.00006 | $0.00209 |
| Sonnet 5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
identity-auth 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 10d 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
Identity, Authentication, and Authorization Testing
On-demand skill for identity-management, authentication, authorization, session, and cryptographic-control testing. The pentest orchestrator routes here when a finding candidate crosses an identity or authorization boundary. Load only the applicable playbook.
When to Use
- A login, registration, password-reset, MFA, session, token, role, or object-ownership boundary is in scope.
- Multiple users or privilege levels are available for differential testing.
- Do not use for general API inventory or business workflow flaws unless an identity boundary is the root cause.
Playbook Routing
| Class | Playbook |
|---|---|
| Authentication Bypass | playbooks/auth-bypass.md |
| IDOR / Broken Object-Level Authorization | playbooks/idor-access-control.md |
| JWT / Token Attacks | playbooks/jwt-attacks.md |
| CSRF | playbooks/csrf.md |
| Unvalidated Redirect | playbooks/redirects-unvalidated.md |
| Cryptographic Issues | playbooks/cryptographic-issues.md |
Common Pitfalls
- Use authorized disposable accounts and compare unauthenticated, low-privilege, and authorized contexts.
- Redact credentials, sessions, and token values in all artifacts.
- Treat a changed status code alone as a candidate; capture the protected resource or state differential needed to prove impact.
Verification Checklist
- Engagement bootstrap and scope validation succeeded.
- The matched playbook alone was loaded and bound to the PTT task.
- Evidence includes the two relevant identity or authorization contexts.
What ships with it
6 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.
- 10d ago First seen · 46 lines · 13 tokens per session scan A 9470fc22d5d2
identity-auth is a skill published in the GitHub repository Strategic-Automation/violin (87 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 417 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 skills, from other repositories
Web Application Security Testing
OWASP Top 10 testing, injection vulnerability detection, API security assessment, authentication testing, and web vulnerability reporting for authorized assessments.
owasp-top-10-testing
Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design…
application-security-testing
Application security testing (AppSec) across a whole product with Strix — decide which asset needs which test (source code, running web app, API, CI pipeline), run it, and turn the results into a ranked remediation plan. Autonomous agents exploit and prove each issue instead of emitting static-analysis alerts, so the…
performing-soap-web-service-security-testing
Perform security testing of SOAP web services by analyzing WSDL definitions and testing for XML injection, XXE, WS-Security bypass, and SOAPAction spoofing.
testing-api-authentication-weaknesses
Tests API authentication mechanisms for weaknesses including broken token validation, missing authentication on endpoints, weak password policies, credential stuffing susceptibility, token leakage in URLs or logs, and session management flaws. The tester evaluates JWT implementation, API key handling, OAuth flows, and…
testing-api-for-mass-assignment-vulnerability
Tests APIs for mass assignment (auto-binding) vulnerabilities where clients can modify object properties they should not have access to by including additional parameters in API requests. The tester identifies writable endpoints, adds undocumented fields to request bodies (role, isAdmin, price, balance), and checks if…