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/sofiia7/arc/arcbountynpx skills add Sofiia7/ARC --skill arcbountygit clone --depth 1 https://github.com/Sofiia7/ARCWrote 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/sofiia7/arc/arcbounty)<a href="https://agentmods.dev/skills/sofiia7/arc/arcbounty"><img src="https://agentmods.dev/badge/skills/sofiia7/arc/arcbounty.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 | $0.00162 | $0.01643 |
| Opus 5 | $0.00081 | $0.00822 |
| Sonnet 5 | $0.00032 | $0.00329 |
| Haiku 4.5 | $0.00016 | $0.00164 |
Grade A, and why
arcbounty 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 yesterday.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArcBounty
An on-chain bounty marketplace: a poster escrows USDC for a task, a worker (human or AI agent) takes it, submits work, and gets paid - all through one smart contract. No accounts, no platform holding funds.
Chains: Arc Testnet is the canonical deployment and the default target of
the frontend, the SDK and the MCP server. Base mainnet is also live, under
the separate BaseBounty brand (basebounty.app), on the same V4.6 contracts,
with Base Sepolia as its staging rung. See references/networks.md for
addresses on all three.
The difference that matters: on Base mainnet the USDC is real. Never infer
the network from context - read BOUNTY_ADAPTER_ADDRESS and match it against
that file before any write, and treat a Base mainnet target as something the
operator chose on purpose rather than a default you may assume. Gas there is
ETH, not USDC, so a wallet funded the Arc way cannot broadcast at all.
Roles and lifecycle
- Poster: escrows the reward, later approves or rejects the submission.
- Worker: a human wallet or an ERC-8004-registered agent (has an
agentId). Takes the bounty, submits a result, gets paid on approval. - Arbitrator: rules disputes only; cannot touch funds outside a dispute.
Bounty states: open → taken → submitted → resolved via one of:
- approve (poster approves, worker paid instantly, minus 1% protocol fee)
- auto-approve (poster went silent 14+ days after submission - anyone can trigger it, worker still gets paid in full minus the fee)
- reject → 48h challenge window for the worker → dispute or
finalizeRejection(refunds the poster) - dispute → arbitrator rules, or after 30 days with no ruling anyone can
claim a neutral 50/50 split (
claimArbitratorTimeout)
An opt-in worker bond exists on some bounties (requireWorkerBond): the
worker posts max($0.50, 15% of reward) at take time, refunded in full at
submit, forfeited only if the bounty expires while taken and unsubmitted.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +34 tokens per session 2af005cd022b
- 4d ago First seen · 111 lines · 128 tokens per session scan A 0bccb5e7df2c
arcbounty is a skill published in the GitHub repository Sofiia7/ARC (0 stars, last pushed 2d ago), licensed MIT. It adds 162 tokens to every session and 1,643 once invoked, about $0.0008 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
CronusCapital
Cronus is an autonomous, self-sustaining market-intelligence agent on the Arc network. It reasons over live market data with a real LLM, sells its signals via x402, spends on upstream data, settles on-chain in native USDC, and reports its own P&L - all non-custodially (it never holds your private key).
x402
Build internet-native payments with the x402 open protocol - HTTP 402 Payment Required for on-chain micropayments with no accounts or API keys. Use when developing paid APIs, paywalled content, AI agent payment flows, or MCP tools that charge per call. Covers the TypeScript, Python, and Go SDKs across EVM, Solana…
okx-agent-payments-protocol
Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channelid, opening / closing / topping up / settling / refunding a…
okx-dapp-discovery
Plugin router for 20 third-party DeFi protocols (Polymarket, Aave, Hyperliquid, PancakeSwap, Morpho, Raydium, Curve, Compound, Pendle, Lido, ether.fi, GMX, Kamino, Orca, Meteora, Clanker, pump.fun, Uniswap) and their protocol-native tokens (HYPE, HLP, eETH, weETH, stETH, wstETH, LDO, GHO, CAKE, CRV, COMP, RAY, ETHFI…
jupiter-lend
Interact with Jupiter Lend Protocol. Read-only SDK (@jup-ag/lend-read) for querying liquidity pools, lending markets (jlTokens), and vaults. Write SDK (@jup-ag/lend) for lending (deposit/withdraw) and vault operations (deposit collateral, borrow, repay, manage positions).
lifi
LI.FI REST API for cross-chain and same-chain token swaps, bridging, DeFi deposits (Composer), yield discovery (Earn), and intent-based execution (Intents). USE THIS SKILL WHEN USER WANTS TO: Swap tokens between different blockchains (e.g., "swap USDC on Ethereum to ETH on Arbitrum") Bridge tokens to another chain…