vibe-coding-cn is a Chinese tutorial on using AI as a programming partner, covering prompts, reusable skills, workflows, context management, and software engineering practices. It guides developers from an initial idea through implementation and verification with AI coding tools such as Claude Code and Codex. The catalogue entries are the project’s documented skills, instruction, plugin, and command for applying this workflow.
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.
npx skills add tradecatlabs/vibe-coding-cn --skill web3-poc-foundrygit clone --depth 1 https://github.com/tradecatlabs/vibe-coding-cnWrote 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/tradecatlabs/vibe-coding-cn/web3-poc-foundry)<a href="https://agentmods.dev/skills/tradecatlabs/vibe-coding-cn/web3-poc-foundry"><img src="https://agentmods.dev/badge/skills/tradecatlabs/vibe-coding-cn/web3-poc-foundry/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/tradecatlabs/vibe-coding-cn/web3-poc-foundry"><img src="https://agentmods.dev/badge/skills/tradecatlabs/vibe-coding-cn/web3-poc-foundry.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.00059 | $0.09354 |
| Opus 5 | $0.00030 | $0.04677 |
| Sonnet 5 | $0.00012 | $0.01871 |
| Haiku 4.5 | $0.00006 | $0.00935 |
Grade A, and why
web3-poc-foundry scanned grade A with 0 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 7d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- web3-poc-foundry — 100% identical, 2 lines differ
- web3-poc-foundry — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PoC WRITING + FOUNDRY COMPLETE REFERENCE
Immunefi requires RUNNABLE code. Not pseudocode. Not steps. Running Foundry tests with before/after logs and a passing assert.
QUICK START
# Immunefi official templates (preferred for submissions)
forge init my-poc --template immunefi-team/forge-poc-templates --branch default
forge init my-poc --template immunefi-team/forge-poc-templates --branch reentrancy
forge init my-poc --template immunefi-team/forge-poc-templates --branch flash_loan
forge init my-poc --template immunefi-team/forge-poc-templates --branch price_manipulation
# Or blank Foundry project
forge init my-poc
cd my-poc
# Setup .env
echo "MAINNET_RPC_URL=https://eth.llamarpc.com" > .env
echo "BASE_RPC_URL=https://base.llamarpc.com" >> .env
echo "ARB_RPC_URL=https://arb1.arbitrum.io/rpc" >> .env
# Run exploit
source .env
forge test --match-test testExploit -vvvv --fork-url $MAINNET_RPC_URL
STANDARD PoC TEMPLATE (Production Quality for Immunefi)
// SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.10;
import "forge-std/Test.sol";
import "forge-std/console.sol";
/**
* @title [Protocol Name] - [Bug Description]
* @notice PoC for Immunefi submission
* @dev Demonstrates [impact] by exploiting [root cause]
*
* Vulnerable contract: [address] ([name])
* Vulnerable function: [functionName]
* Immunefi program: [URL]
* Severity: [Critical/High/Medium/Low]
*/
// Minimal interfaces — only what you need
interface IVulnProtocol {
function deposit(uint256 amount) external;
function withdraw(uint256 amount) external;
function balanceOf(address) external view returns (uint256);
}
interface IERC20 {
function approve(address, uint256) external returns (bool);
function balanceOf(address) external view returns (uint256);
function transfer(address, uint256) external returns (bool);
function transferFrom(address, address, uint256) external returns (bool);
}
contract ExploitPoC is Test {
// ============================================================
// CONFIGURATION
// ============================================================
uint256 constant ATTACK_BLOCK = 18_000_000; // pin block for reproducibility
address constant VULN_CONTRACT = 0x...;
address constant TOKEN = 0x0000000000000000000000000000000000000000; // example token placeholder
IVulnProtocol vuln = IVulnProtocol(VULN_CONTRACT);
IERC20 token = IERC20(TOKEN);
// ============================================================
// SETUP
// ============================================================
function setUp() public {
vm.createSelectFork(vm.envString("MAINNET_RPC_URL"), ATTACK_BLOCK);
vm.label(VULN_CONTRACT, "VulnerableProtocol");
vm.label(TOKEN, "USDC");
vm.label(address(this), "Attacker");
}
// ============================================================
// EXPLOIT
// ============================================================
function testExploit() public {
uint256 attackerBefore = token.balanceOf(address(this));
uint256 protocolBefore = token.balanceOf(VULN_CONTRACT);
console.log("=== INITIAL STATE ===");
console.log("Attacker USDC: ", attackerBefore);
console.log("Protocol USDC: ", protocolBefore);
console.log("--------------------");
// Step 1: [description]
deal(TOKEN, address(this), 1e6); // 1 USDC starting capital
// Step 2: [description]
token.approve(VULN_CONTRACT, type(uint256).max);
vuln.deposit(1e6);
// Step 3: [the exploit]
// ... exploit logic ...
uint256 attackerAfter = token.balanceOf(address(this));
uint256 protocolAfter = token.balanceOf(VULN_CONTRACT);
console.log("=== FINAL STATE ===");
console.log("Attacker USDC: ", attackerAfter);
console.log("Protocol USDC: ", protocolAfter);
console.log("Profit: ", attackerAfter - attackerBefore);
console.log("Protocol loss: ", protocolBefore - protocolAfter);
assertGt(attackerAfter, attackerBefore, "Exploit failed: no profit");
}
}
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.
- 7d ago First seen · 1,137 lines · 59 tokens per session scan A 90e5f0bf622a
web3-poc-foundry is a skill published in the GitHub repository tradecatlabs/vibe-coding-cn (16,338 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 9,354 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-15.
Other skills, from other repositories
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
promptfoo-redteam-setup
Create or refine a Promptfoo redteam config and generate probes from target behavior, code, or OpenAPI evidence. Use for purpose, trust boundaries, plugins, strategies, and grading guidance. Use promptfoo-provider-setup for connection work and promptfoo-redteam-run for an existing scan.
promptfoo-provider-setup
Connect Promptfoo to a model, live HTTP API, local Python/JavaScript provider, or app code. Use for request/auth mapping, response parsing, OpenAPI setup, and connection smoke tests. Use promptfoo-evals for broader eval coverage and promptfoo-redteam-setup for attack selection.
promptfoo-redteam-run
Execute, inspect, and rerun an existing Promptfoo redteam scan. Use for generated YAML, result exports, attack success rates, grader/target errors, filtered reruns, and CI gates. Use promptfoo-provider-setup for connections and promptfoo-redteam-setup for new scan plans.
discount-review
Inspect the discount policy fixture with a repeatable review checklist and helper script.
code-review
Reviews code for bugs, security issues, and best practices.