agentleFS
Sign inStart free
Strategic-AutomationStrategic-Automation/violin/skills/business-logic/SKILL.md

business-logic

Skill159 starsChanged 52 days agoMITView on GitHub

Test workflows, state transitions, pricing, and concurrency.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use open-redirect, nosql-injection and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • yaklangSkill

    open-redirect

    Open redirect playbook. Use when URL parameters, form actions, or JavaScript sinks control navigation targets and may redirect users to attacker-controlled destinations.

    Also in 4 projects that use this

  • blacklanternsecuritySkill

    nosql-injection

    Guide NoSQL injection exploitation during authorized penetration testing.

    Also in 3 projects that use this

  • yaklangSkill

    prototype-pollution

    Prototype pollution testing for JavaScript stacks. Use when user input is merged into objects (query parsers, JSON bodies, deep assign), when configuring libraries via untrusted keys, or when hunting RCE gadgets via polluted Object.prototype in Node or the browser.

    Also in 3 projects that use this

  • VercelSkill

    oauth

    Configure OAuth providers (Google, Apple, Microsoft, Facebook, GitHub, etc.) to work with portless local dev URLs. Use when setting up OAuth redirect URIs, fixing "redirect_uri_mismatch" or "invalid redirect" errors, configuring sign-in providers for local development, or when a provider rejects .localhost subdomains. Triggers include "OAuth not working with portless", "redirect URI mismatch", "Google/Apple/Microsoft sign-in fails locally", "configure OAuth for local dev", or any task involving OAuth callback URLs with portless domains.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not use for mass assignment, IDOR, or API inventory when those are the root cause.

    line 22
  2. Distinctive:

    Prefer disposable accounts, preview endpoints, and reversible actions.

    line 33
  3. Distinctive:

    Do not complete transactions, deplete stock, or alter third-party data without explicit approval.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-testing or identity-auth first.

Playbook Routing

ClassPlaybook
Workflow bypass, pricing, coupon, quota, referral, or race-condition flawplaybooks/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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free