Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/woohyun212/security-skillnpx agentmods add skills/woohyun212/security-skill/property-based-testingWrote 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/woohyun212/security-skill/property-based-testing)<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/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/woohyun212/security-skill/property-based-testing"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/property-based-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00027 | $0.02797 |
| Opus 5.5 | $0.00011 | $0.01119 |
| Sonnet 5.5 | $0.00005 | $0.00559 |
| Haiku 4.5 | $0.00003 | $0.00280 |
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 1mo 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 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 |
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.
- 1mo ago First seen · 303 lines · 27 tokens per session scan B 122684b94ab8
property-based-testing is a skill published in the GitHub repository woohyun212/security-skill (22 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 2,797 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.