Deepsec Documentation Guide
vercel-labs/deepsec
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
Test payment decision and value-movement invariants with authorized synthetic instruments and reversible sandbox transactions.
Install Test Payment Fraud Controls
$ npx skills add cyberful/cyberful --skill test-payment-fraud-controls -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cyberful/cyberful test-payment-fraud-controls --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/test-payment-fraud-controls .claude/skills/test-payment-fraud-controls && rm -rf skills-srcUse ~/.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/
Install the "test-payment-fraud-controls" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/test-payment-fraud-controls into .claude/skills/test-payment-fraud-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-payment-fraud-controls", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/test-payment-fraud-controlsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cyberful/cyberful --skill test-payment-fraud-controls -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cyberful/cyberful test-payment-fraud-controls --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cyberful/builtin/skills/test-payment-fraud-controls .agents/skills/test-payment-fraud-controls && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-payment-fraud-controls" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/test-payment-fraud-controls into .agents/skills/test-payment-fraud-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-payment-fraud-controls", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cyberful/cyberful --skill test-payment-fraud-controls -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cyberful/cyberful test-payment-fraud-controls --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cyberful/builtin/skills/test-payment-fraud-controls .cursor/skills/test-payment-fraud-controls && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "test-payment-fraud-controls" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/test-payment-fraud-controls into .cursor/skills/test-payment-fraud-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-payment-fraud-controls", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cyberful/cyberful.git --path cyberful/builtin/skills/test-payment-fraud-controls--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cyberful/cyberful --skill test-payment-fraud-controls -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cyberful/cyberful test-payment-fraud-controls --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cyberful/builtin/skills/test-payment-fraud-controls .gemini/skills/test-payment-fraud-controls && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "test-payment-fraud-controls" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/test-payment-fraud-controls into .gemini/skills/test-payment-fraud-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-payment-fraud-controls", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cyberful/cyberful test-payment-fraud-controlsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cyberful/cyberful --skill test-payment-fraud-controls -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .github/skills && cp -r skills-src/cyberful/builtin/skills/test-payment-fraud-controls .github/skills/test-payment-fraud-controls && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "test-payment-fraud-controls" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/test-payment-fraud-controls into .github/skills/test-payment-fraud-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-payment-fraud-controls", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cyberful/cyberful --skill test-payment-fraud-controls -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cyberful/cyberful test-payment-fraud-controls --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cyberful/builtin/skills/test-payment-fraud-controls .opencode/skills/test-payment-fraud-controls && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "test-payment-fraud-controls" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/test-payment-fraud-controls into .opencode/skills/test-payment-fraud-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-payment-fraud-controls", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
test-payment-fraud-controls- GitHub stars
- 135
- Token cost
- ~668 tokens
- SKILL.md length
- 232 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 85
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Test payment decision and value-movement invariants with authorized synthetic instruments and reversible sandbox transactions.
- Threshold abuse controls
- SKILL.md covers Define the invariant matrix, Execute bounded comparisons and Prove the effect
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Test Payment Fraud Controls is an agent skill from cyberful/cyberful. Test payment decision and value-movement invariants with authorized synthetic instruments and reversible sandbox transactions. Use for card, transfer, refund, payout, and threshold abuse controls.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `agents/openai.yaml`, `assets/payment-control-matrix.schema.json` and `assets/payment-control-matrix.template.json`).
It sits in Security. 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
- Threshold abuse controls
Example prompts
- “/test-payment-fraud-controls”
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
No scripts in the folder and no shell commands in SKILL.md.
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 Payment Fraud Controls loads about 668 tokens when it runs, and up to ~1k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 232 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 232 words, ~668 tokens.
Download SKILL.mdSave it as
.claude/skills/test-payment-fraud-controls/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- test-payment-fraud-controls
- description
- Test payment decision and value-movement invariants with authorized synthetic instruments and reversible sandbox transactions. Use for card, transfer, refund, payout, and threshold abuse controls.
- metadata.domain
- application-security
- metadata.subdomain
- payment-fraud-controls
- metadata.triggers
- payment fraud testing, card testing controls, transfer fraud controls, refund abuse testing, payment threshold testing, payout control testing
- metadata.tags
- payments, card-testing, transfer, refund, threshold, fraud, MITRE-F3
Test Payment Fraud Controls
Test payment and value-movement invariants only with explicitly authorized sandbox rails, synthetic instruments, tester-controlled beneficiaries, bounded value, and a verified cleanup or reversal path. Do not use production customer instruments or create real merchant, issuer, or customer harm.
Define the invariant matrix
Read references/payment-control-testing.md for lifecycle-specific evidence and stopping conditions. Copy assets/payment-control-matrix.template.json and preserve assets/payment-control-matrix.schema.json when coordinating more than a few cases.
Cover the smallest discriminating set across instrument state, actor state, beneficiary age, value band, velocity, channel, device or session context, policy version, and lifecycle stage. Name the expected decision and durable effect before executing a case.
Execute bounded comparisons
Use paired controls that change one relevant dimension. Exercise authorization, capture, transfer, payout, refund, reversal, dispute, or threshold behavior only when each operation is permitted and reversible. Stop on unexpected real settlement, non-synthetic data, uncontrolled beneficiary routing, rate-control activation beyond the approved ceiling, or inability to verify authoritative state.
Prove the effect
Collect the risk decision and reasons, enforcement result, processor or rail response, transaction state, authoritative ledger delta, idempotency record, and cleanup result. An HTTP success, processor decline, or UI message alone is not a finding. Confirm a repeatable invariant violation and its net durable value effect.
Map only demonstrated behavior to MITRE F3: card-testing behavior to F1012, improper reversal abuse to F1043, and threshold probing to F1046. Omit the mapping when the observed mechanism differs.
© 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 4 other files (references, assets) in cyberful/builtin/skills/test-payment-fraud-controls of cyberful/cyberful.
- SKILL.md
- agents/openai.yaml
- assets/payment-control-matrix.schema.json
- assets/payment-control-matrix.template.json
- references/payment-control-testing.md
Open the folder on GitHubat commit ec598a6
Compare with similar skills
Test Payment Fraud Controls 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Test Payment Fraud Controls this skillcyberful/cyberful | 135 | — | ~668 | Automated safety check: Pass | AGPL-3.0 | |
| Deepsec Documentation Guidevercel-labs/deepsec | 8.1k | — | ~956 | Automated safety check: Pass | Apache-2.0 | |
| Skill Scannergetsentry/skills | 1k | 4 repos | ~2.5k | Automated safety check: Warn | Apache-2.0 | |
| Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit | 481 | 1 repos | ~3.3k | Automated safety check: Pass | None | |
| Security Alert Triageelastic/agent-skills | 592 | 1 repos | ~3.5k | Automated safety check: Notes | Apache-2.0 | |
| Shiro Attack CLISummerSec/ShiroAttack2 | 2.6k | — | ~945 | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Skill Scanner
getsentry/skills
Scan agent skills for security issues. An agent skill from getsentry/skills.
Serenity Aleabitoreddit
yan-labs/serenity-aleabitoreddit
Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.
- Official
Security Alert Triage
elastic/agent-skills
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
Shiro Attack CLI
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
Cve Remediation
rundeck/rundeck
Verify if a CVE affects the project and remediate it. An agent skill from rundeck/rundeck.
More from cyberful/cyberful
All 85 skills in this repoAudit Infrastructure As Code
cyberful/cyberful
Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.
Audit Kubernetes Policy Enforcement
cyberful/cyberful
Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.
Audit Pci Dss Penetration Test Evidence
cyberful/cyberful
Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.
Operate Content Discovery
cyberful/cyberful
Design and interpret advanced content discovery with ffuf and complementary web fuzzers.
Operate Network Recon
cyberful/cyberful
Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.
Operate Sast Toolchain
cyberful/cyberful
Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.
Related
Categories
Questions about Test Payment Fraud Controls
What does Test Payment Fraud Controls do?
Test payment decision and value-movement invariants with authorized synthetic instruments and reversible sandbox transactions. Test Payment Fraud Controls is an agent skill from cyberful/cyberful. Test payment decision and value-movement invariants with authorized synthetic instruments and reversible sandbox transactions.
When should I use Test Payment Fraud Controls?
Test Payment Fraud Controls fits situations like: threshold abuse controls.
How do I install Test Payment Fraud Controls in Claude Code?
Run `npx skills add cyberful/cyberful --skill test-payment-fraud-controls -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/test-payment-fraud-controls in cyberful/cyberful) into .claude/skills/test-payment-fraud-controls in your project. Claude Code loads it when a task matches its description.
How do I install Test Payment Fraud Controls in Codex?
Run `npx skills add cyberful/cyberful --skill test-payment-fraud-controls -a codex`. Or copy the skill folder (cyberful/builtin/skills/test-payment-fraud-controls in cyberful/cyberful) into .agents/skills/test-payment-fraud-controls in your project. Codex loads it when a task matches its description.
Can I use Test Payment Fraud Controls 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-payment-fraud-controls -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-payment-fraud-controls, .gemini/skills/test-payment-fraud-controls, .github/skills/test-payment-fraud-controls and .opencode/skills/test-payment-fraud-controls in your project.
What does Test Payment Fraud Controls need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Payment Fraud Controls is instructions for the agent only.
Does Test Payment Fraud Controls 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 Payment Fraud Controls 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. Review the folder before installing.
What licence does Test Payment Fraud Controls use?
Test Payment Fraud Controls 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 Payment Fraud Controls use?
About 668 tokens (SKILL.md is roughly 2.7k 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 372 tokens, read only when the agent opens those files.
What are the alternatives to Test Payment Fraud Controls?
Skills that share tags, products or a category with Test Payment Fraud Controls: Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars), Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 481 stars) and Security Alert Triage (elastic/agent-skills, 592 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Payment Fraud Controls?
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.