property-based-testing

property-based-testing is a skill for Claude Code, Codex from woohyun212/security-skill. It costs 27 tokens per session (2,797 once invoked), scanned B, original, MIT.

A guide for testing software with automatically generated inputs instead of only hand-written examples. Property-based testing checks rules that should always remain true, such as safe parsing or correct access control.

In plain words
What is it for?
Use it to test cryptography, parsers, serialization, smart contracts, and code with large input ranges across Python, Rust, JavaScript or TypeScript, Solidity, and Go.
Why use it?
It can expose unusual inputs and security edge cases that a small set of example tests may miss. It can also help reduce a failure to a smaller reproducible input.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/woohyun212/security-skill/property-based-testing
Any agent
npx skills add woohyun212/security-skill --skill property-based-testing
Clone the repo
git clone --depth 1 https://github.com/woohyun212/security-skill

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for property-based-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/woohyun212/security-skill/property-based-testing.svg)](https://agentmods.dev/skills/woohyun212/security-skill/property-based-testing)
Your own site
<a href="https://agentmods.dev/skills/woohyun212/security-skill/property-based-testing"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/property-based-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,797 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.02797
Opus 5 $0.00014 $0.01399
Sonnet 5 $0.00005 $0.00559
Haiku 4.5 $0.00003 $0.00280

Measured 4d ago against content hash 122684b94ab8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

property-based-testing scanned grade B with 2 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 4d 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.

Downloads and executes remote codemediumSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -L https://foundry.paradigm.xyz | bash

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -L https://foundry.paradigm.xyz | bash
property-based-testing/SKILL.md · 303 lines

How it starts

The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.

What this skill does

Guides property-based testing (PBT) across Python, Rust, JavaScript/TypeScript, Solidity, and Go to surface security-relevant edge cases that example-based unit tests systematically miss. Rather than asserting that specific inputs produce specific outputs, PBT defines invariants the system must always satisfy — then lets a framework generate hundreds or thousands of inputs to try to break them. This skill covers property identification, framework selection, test writing, counterexample minimization, and failure triage with a focus on overflow/underflow, deserialization roundtrips, access control invariants, and state machine violations.

When to use

  • When auditing cryptographic primitives, parsers, or serialization libraries for correctness under adversarial input
  • When reviewing smart contracts for arithmetic invariants before or alongside a formal audit
  • When a function has a large or unbounded input domain that example tests cannot adequately cover
  • When debugging a known crash and needing a minimal reproducible input automatically
  • When adding regression coverage to a function that previously had a security-relevant bug

Prerequisites

Install the framework for the target language:

Python — Hypothesis

pip install hypothesis
# Optional: pytest integration
pip install pytest hypothesis

Rust — proptest

# Cargo.toml
[dev-dependencies]
proptest = "1"

JavaScript / TypeScript — fast-check

npm install --save-dev fast-check
# or
yarn add --dev fast-check

Solidity — Foundry fuzz testing

curl -L https://foundry.paradigm.xyz | bash
foundryup

Go — testing/quick (stdlib)

import "testing/quick"
// No additional installation required

Inputs

Variable Required Description
PBT_TARGET_FILE required Path to the source file or contract under test
PBT_LANGUAGE required Target language: python, rust, js, solidity, go
PBT_ITERATIONS optional Number of test cases to generate (default: framework default, typically 100)
PBT_OUTPUT_DIR optional Directory to save failing counterexamples (default: ./pbt-output)
PBT_SEED optional Fixed seed for reproducible runs

Read the full file on GitHub · 303 lines

Changes

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.

  1. 4d ago First seen · 303 lines · 27 tokens per session scan B 122684b94ab8

Subscribe to this mod's changes

property-based-testing is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 2,797 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens