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 business-logicgit 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/business-logic)<a href="https://agentmods.dev/skills/strategic-automation/violin/business-logic"><img src="https://agentmods.dev/badge/skills/strategic-automation/violin/business-logic/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/business-logic"><img src="https://agentmods.dev/badge/skills/strategic-automation/violin/business-logic.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.00015 | $0.00363 |
| Opus 5 | $0.00008 | $0.00181 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
business-logic 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 11d 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
Business Logic Security Testing
On-demand skill for application-specific rules and state transitions that technical vulnerability taxonomies do not fully describe. It owns the single canonical business-logic playbook; do not duplicate workflow, pricing, coupon, or race-condition procedures in other skills.
When to Use
- An application has multi-step workflows, pricing, quotas, inventory, coupons, referrals, approvals, or state transitions.
- A candidate depends on violating an intended business rule rather than exploiting a parser or authorization check alone.
- Do not use for mass assignment, IDOR, or API inventory when those are the root cause; route to
api-testingoridentity-authfirst.
Playbook Routing
| Class | Playbook |
|---|---|
| Workflow bypass, pricing, coupon, quota, referral, or race-condition flaw | playbooks/workflow-state-abuse.md |
Common Pitfalls
- Map the expected state machine and record a clean baseline before mutating a field or sequence.
- Prefer disposable accounts, preview endpoints, and reversible actions.
- Do not complete transactions, deplete stock, or alter third-party data without explicit approval.
Verification Checklist
- Engagement bootstrap and scope validation succeeded.
- The expected workflow and attempted invalid transition are documented.
- Evidence shows the baseline, mutation, and resulting rule violation.
What ships with it
1 file 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.
- 11d ago First seen · 41 lines · 15 tokens per session scan A d67e5edddbfa
business-logic is a skill published in the GitHub repository Strategic-Automation/violin (88 stars, last pushed 7d ago), licensed MIT. It adds 15 tokens to every session and 363 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-api-security-testing-with-postman
Uses Postman to perform structured API security testing by building collections that test for OWASP API Security Top 10 vulnerabilities including authentication bypass, authorization flaws, injection, and data exposure. The tester creates environments with multiple user roles, writes test scripts for automated…
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…