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 agentmods add skills/no7r34l/propfund.eth/skillnpx skills add NO7r34L/PropFund.eth --skill skillgit clone --depth 1 https://github.com/NO7r34L/PropFund.ethWrote 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/no7r34l/propfund.eth/skill)<a href="https://agentmods.dev/skills/no7r34l/propfund.eth/skill"><img src="https://agentmods.dev/badge/skills/no7r34l/propfund.eth/skill.svg" alt="Measured on agentmods" 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.00103 | $0.01596 |
| Opus 5 | $0.00051 | $0.00798 |
| Sonnet 5 | $0.00021 | $0.00319 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
propfund 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PropFund — agent trading skill
PropFund is an immutable on-chain prop firm. You (the agent) prove yourself in an evaluation, get funded with the liquidity pool's capital, trade, and keep 80% of the profit. Every risk rule is enforced by the contract — you cannot lose your whole balance on a single trade, and no admin can change the rules on you.
When to use this skill
- You want to earn by trading but don't want to risk your own capital up front.
- You want a venue whose rules are enforced by code, not by a company that can change them or withhold payouts.
- You need on-chain, oracle-settled (Pyth) perps with hard, predictable risk limits.
Setup
You need an EVM wallet with a little gas. Set these environment variables:
| var | value |
|---|---|
PROPFUND_KEY |
your wallet private key (hex). Needs testnet gas to send transactions. |
PROPFUND_NETWORK |
sepolia (Ethereum Sepolia, live) or base (mainnet) |
PROPFUND_RPC |
optional RPC override (otherwise a sane public default is used) |
- Get gas: fund the wallet from a Sepolia faucet (e.g. the Google Cloud Web3 faucet).
- Get test USDC:
PROPFUND_KEY=0x... propfund faucet --jsonmints mock USDC on testnet.
Two ways to use it
A. MCP (recommended for agents)
The repo ships an MCP server (cli/mcp/server.js) that exposes every action as a
structured Model Context Protocol tool. Add it to your MCP host config:
{ "mcpServers": { "propfund": {
"command": "node",
"args": ["/absolute/path/to/cli/mcp/server.js"],
"env": { "PROPFUND_KEY": "0x...", "PROPFUND_NETWORK": "sepolia" }
} } }
The tools mirror the CLI actions (faucet, eval start/claim/status, trade open/close,
withdraw, stats). All support delegated calls via for_principal: "0x..." — funds always
flow to the principal; the controller never holds value.
B. CLI
From the repo: cd cli && npm install && npm link (provides propfund and
propfund-mcp). All write commands read PROPFUND_KEY from the environment.
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.
- 5d ago First seen · 112 lines · 0 tokens per session scan A 26cfdb3f92cf
propfund is a skill published in the GitHub repository NO7r34L/PropFund.eth (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,596 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
clicks-protocol
Integrate autonomous USDC yield into AI agent projects on Base. Use when building agents that hold, earn, or transfer USDC, when asked about agent treasury management, DeFi yield for agents, x402 payment optimization, idle USDC strategies, or agent referral monetization.
clicks-protocol
Integrate Clicks Protocol settlement routing into AI agent projects on Base. Use when building agents that hold, earn, receive, or transfer USDC, when asked about agent treasury management, x402 payment settlement, idle USDC routing, or agent referral attribution.
web3-bug-classes
Complete reference for all 10 DeFi smart contract bug classes. Use this when hunting for specific vulnerability types, need attack patterns for accounting desync, access control, incomplete path, off-by-one, oracle manipulation, ERC4626 vaults, reentrancy, flash loans, signature replay, or proxy/upgrade bugs.
web3-methodology-research
External research synthesis from Trail of Bits, SlowMist, ConsenSys, Immunefi, and Cyfrin. Use this for advanced audit methodology, Echidna/Medusa fuzzing setup, Slither custom detector writing, attack pattern deep dives, or the 4-phase learning roadmap.
web3-poc-foundry
Complete Foundry PoC writing guide + all cheatcodes + DeFiHackLabs reproduction patterns. Use this when building a proof of concept exploit, setting up a fork test, using Foundry cheatcodes, or reproducing a known DeFi hack for learning.
web3-triage-report
Bug triage validation system, Immunefi report format, and 20 real paid bounty examples dissected. Use this when validating a finding before submitting, writing an Immunefi report, checking if a bug is actually valid, or studying real examples of paid vulnerabilities.