Agent skill

Test Concurrency Resource Abuse

by cyberful in cyberful/cyberful

Assess race conditions, transactional invariants, idempotency, retries, replay, rate and quota enforcement, algorithmic complexity, resource amplification, and cost abuse during authorized…

AGPL-3.0Auto-check passedDevelopment

Install Test Concurrency Resource Abuse

skills CLI
$ npx skills add cyberful/cyberful --skill test-concurrency-resource-abuse -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cyberful/cyberful test-concurrency-resource-abuse --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/test-concurrency-resource-abuse .claude/skills/test-concurrency-resource-abuse && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-concurrency-resource-abuse
GitHub stars
135
Token cost
~1.1k tokens
SKILL.md length
431 words
Files
10 (incl. scripts, references, assets)
Skills in repo
85
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Assess race conditions, transactional invariants, idempotency, retries, replay, rate and quota enforcement, algorithmic complexity, resource amplification, and cost abuse during authorized…

  • Works in 6 steps: Create a tester-owned object in a known… → Synchronize requests as close to the… → Vary concurrency, connection reuse,… → …
  • Duplicate redemption
  • SKILL.md covers Define the Invariant and…, Build a Deterministic Race…, Test Replay and Retry Boundaries and Measure Amplification, plus 1 more section
  • Runs Python scripts from its folder

What it does

Test Concurrency Resource Abuse is an agent skill from cyberful/cyberful. Assess race conditions, transactional invariants, idempotency, retries, replay, rate and quota enforcement, algorithmic complexity, resource amplification, and cost abuse during authorized penetration tests or code audits. Use for TOCTOU, double spend, duplicate redemption, limit bypass, ReDoS, decompression bombs, fan-out, pagination, batch, queue, storage, compute, and unbounded-consumption risks.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including scripts, reference files and assets (for example `agents/openai.yaml`, `assets/concurrency-evidence.schema.json` and `assets/concurrency-probe.example.json`).

It sits in Development, covering Async programming. The repository describes itself as: Cyberful is an open-source AI Red Team for discovering, exploiting, verifying, and remediating vulnerabilities. The licence is AGPL-3.0.

When your agent uses it

  • Duplicate redemption
  • Decompression bombs
  • Unbounded-consumption risks

Example prompts

  • “/test-concurrency-resource-abuse”

Requirements

  • Python 3
  • Docker

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Create a tester-owned object in a known state.
  2. Synchronize requests as close to the final commit point as possible.
  3. Vary concurrency, connection reuse, protocol, and arrival ordering.
  4. Record every response, durable state, side effect, and asynchronous event.
  5. Reconcile after queues and external processors settle.
  6. Repeat with a matched sequential control.

What it can do on your machine

Read from SKILL.md and the folder at commit ec598a6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Concurrency Resource Abuse loads about 1.1k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 109 tokens; SKILL.md has 431 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 431 words, ~1,131 tokens.

Download SKILL.mdSave it as .claude/skills/test-concurrency-resource-abuse/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
test-concurrency-resource-abuse
description
Assess race conditions, transactional invariants, idempotency, retries, replay, rate and quota enforcement, algorithmic complexity, resource amplification, and cost abuse during authorized penetration tests or code audits. Use for TOCTOU, double spend, duplicate redemption, limit bypass, ReDoS, decompression bombs, fan-out, pagination, batch, queue, storage, compute, and unbounded-consumption risks.
metadata.domain
application-security
metadata.subdomain
concurrency-and-resource-abuse
metadata.triggers
concurrency abuse test, race condition probe, idempotency bypass, resource amplification, quota or rate limit bypass
metadata.tags
race-condition, TOCTOU, idempotency, resource-exhaustion, rate-limits, cost-abuse

Test Concurrency and Resource Abuse

Define the Invariant and Resource

Write the invariant before generating load: one redemption per entitlement, nonnegative balance, one active primary owner, monotonic state, bounded work per principal, or finite cost per request.

Map every authority that reads or writes it: API handler, database, cache, queue, worker, payment processor, scheduler, webhook, and reconciliation job. Record transaction boundaries, isolation level, uniqueness constraints, locks, compare-and-swap, idempotency stores, retries, and timeout semantics.

Read race-idempotency.md for state races. Read resource-amplification.md for rate, complexity, and cost review.

Build a Deterministic Race Harness

  1. Create a tester-owned object in a known state.
  2. Synchronize requests as close to the final commit point as possible.
  3. Vary concurrency, connection reuse, protocol, and arrival ordering.
  4. Record every response, durable state, side effect, and asynchronous event.
  5. Reconcile after queues and external processors settle.
  6. Repeat with a matched sequential control.

Success is an invariant violation, not merely two successful HTTP responses. Use single-digit concurrency first; precision exposes more than indiscriminate load.

For repeatable active trials in Pentest or Bug Bounty, stage scripts/run_concurrency_probe.py, its manifest, and the probe example. Declare canonical allowed origins plus request and concurrency limits before execution. Literal loopback targets connect directly. Docker service hostnames and other non-loopback targets must use Cyberful's runtime-injected HTTP_PROXY or HTTPS_PROXY; optional trust comes only from runtime SSL_CERT_FILE or CURL_CA_BUNDLE, and TLS verification is never disabled. Secret authorization is accepted only through CYBERFUL_PROBE_AUTHORIZATION. The JSON payload cannot select the route or trust source, and the script is unavailable for Code Audit target traffic. It writes raw bounded responses under the evidence schema; reconcile durable state separately because response success alone never establishes an invariant violation.

Show full SKILL.md (152 more words)Show less

Test Replay and Retry Boundaries

Follow an operation across client retries, gateway retries, queue redelivery, worker crashes, webhook duplication, provider callbacks, and reconciliation. Determine whether the idempotency key is bound to principal, operation, canonical payload, and retention window.

Test same key/different payload, different key/same semantic operation, timeout-before-response, commit-before-crash, and stale replay after state transition.

Measure Amplification

Express cost as a function of controlled input: CPU, memory, database reads or writes, outbound calls, queue items, object count, bytes stored, response bytes, or paid third-party spend. Look for superlinear growth, recursive fan-out, and work performed before authentication, quota, or deduplication.

Rate limits must be evaluated across distributed nodes, alternate endpoints, identities, tenants, IPv4/IPv6, batch sizes, and asynchronous continuations.

Report the Broken Invariant

Include initial state, synchronized sequence, durable final state, externally visible effects, required concurrency, consistency window, and resource cost. Recommend database-enforced invariants, atomic state transitions, bounded work, admission control, and correctly scoped idempotency.

© cyberful, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references, assets) in cyberful/builtin/skills/test-concurrency-resource-abuse of cyberful/cyberful.

  • SKILL.md
  • agents/openai.yaml
  • assets/concurrency-evidence.schema.json
  • assets/concurrency-probe.example.json
  • assets/concurrency-probe.schema.json
  • references/race-idempotency.md
  • references/resource-amplification.md
  • scripts/manifest.json
  • scripts/run_concurrency_probe.py
  • tests/test_run_concurrency_probe.py

Open the folder on GitHubat commit ec598a6

Compare with similar skills

Test Concurrency Resource Abuse next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Concurrency Resource Abuse compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Concurrency Resource Abuse this skillcyberful/cyberful135—~1.1kAutomated safety check: PassAGPL-3.0
Swift Concurrency PerformanceLivsy90/iOS-Performance-Agent-Skills117—~2.9kAutomated safety check: PassMIT
YugabyteDB ASH Instrumentationyugabyte/yugabyte-db11k—~4.5kAutomated safety check: PassCustom licence
Mirage VFS Adapter Authoringstrukto-ai/mirage3.7k—~2.4kAutomated safety check: PassApache-2.0
Golang Patternsantoniopaya22/go-rest-template1729 repos~3.5kAutomated safety check: PassNone
Rust Async Patternsdiodeme/Gold-Band14310 repos~3.1kAutomated safety check: PassAGPL-3.0

Similar skills

  • Swift Concurrency Performance

    Livsy90/iOS-Performance-Agent-Skills

    A skill your agent uses when reviewing Swift Concurrency performance and responsiveness, including task explosions, actor hopping, MainActor bottlenecks, cancellation, AsyncSequence cleanup…

    117 GitHub stars~2.9k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed
  • YugabyteDB ASH Instrumentation

    yugabyte/yugabyte-db

    Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.

    11k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.

    3.7k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Golang Patterns

    antoniopaya22/go-rest-template

    Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

    172 GitHub starsUsed in 9 repos~3.5k tokens
    DevelopmentAuto-check passed
  • Rust Async Patterns

    diodeme/Gold-Band

    Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns.

    143 GitHub starsUsed in 10 repos~3.1k tokens
    DevelopmentAuto-check passed
  • Swift Concurrency

    henrypldev/react-native-nitro-mlx

    Diagnose Swift Concurrency issues, refactor callback-based code to async/await, and guide Swift 6 migration when working with tasks, actors, @MainActor, Sendable, data races, thread safety, or…

    100 GitHub starsUsed in 3 repos~3.1k tokens
    DevelopmentAuto-check passed

More from cyberful/cyberful

All 85 skills in this repo
  • Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.

    135 GitHub stars~649 tokensUpdated 1 mo ago
    Auto-check passed
  • Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.

    135 GitHub stars~610 tokensUpdated 1 mo ago
    Auto-check passed
  • Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.

    135 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed
  • Operate Content Discovery

    cyberful/cyberful

    Design and interpret advanced content discovery with ffuf and complementary web fuzzers.

    135 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Operate Network Recon

    cyberful/cyberful

    Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.

    135 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Operate Sast Toolchain

    cyberful/cyberful

    Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.

    135 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Test Concurrency Resource Abuse

What does Test Concurrency Resource Abuse do?

Assess race conditions, transactional invariants, idempotency, retries, replay, rate and quota enforcement, algorithmic complexity, resource amplification, and cost abuse during authorized…. Test Concurrency Resource Abuse is an agent skill from cyberful/cyberful. Assess race conditions, transactional invariants, idempotency, retries, replay, rate and quota enforcement, algorithmic complexity, resource amplification, and cost abuse during authorized penetration tests or code audits.

When should I use Test Concurrency Resource Abuse?

Test Concurrency Resource Abuse fits situations like: duplicate redemption; decompression bombs; unbounded-consumption risks.

How do I install Test Concurrency Resource Abuse in Claude Code?

Run `npx skills add cyberful/cyberful --skill test-concurrency-resource-abuse -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/test-concurrency-resource-abuse in cyberful/cyberful) into .claude/skills/test-concurrency-resource-abuse in your project. Claude Code loads it when a task matches its description.

How do I install Test Concurrency Resource Abuse in Codex?

Run `npx skills add cyberful/cyberful --skill test-concurrency-resource-abuse -a codex`. Or copy the skill folder (cyberful/builtin/skills/test-concurrency-resource-abuse in cyberful/cyberful) into .agents/skills/test-concurrency-resource-abuse in your project. Codex loads it when a task matches its description.

Can I use Test Concurrency Resource Abuse in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cyberful/cyberful --skill test-concurrency-resource-abuse -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-concurrency-resource-abuse, .gemini/skills/test-concurrency-resource-abuse, .github/skills/test-concurrency-resource-abuse and .opencode/skills/test-concurrency-resource-abuse in your project.

What does Test Concurrency Resource Abuse need to run?

Going by SKILL.md and its folder, Test Concurrency Resource Abuse needs Python for the scripts in its folder. Our summary lists: Python 3; Docker.

Does Test Concurrency Resource Abuse access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Test Concurrency Resource Abuse safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Test Concurrency Resource Abuse use?

Test Concurrency Resource Abuse is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Concurrency Resource Abuse use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Test Concurrency Resource Abuse?

Skills that share tags, products or a category with Test Concurrency Resource Abuse: Swift Concurrency Performance (Livsy90/iOS-Performance-Agent-Skills, 117 stars), YugabyteDB ASH Instrumentation (yugabyte/yugabyte-db, 11k stars), Mirage VFS Adapter Authoring (strukto-ai/mirage, 3.7k stars) and Golang Patterns (antoniopaya22/go-rest-template, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Concurrency Resource Abuse?

cyberful (a GitHub organization) maintains it in cyberful/cyberful, which has 135 GitHub stars. The repository holds 85 skills in this directory. The repository was last updated on August 24, 2026.

Source: cyberful/cyberful on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.