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/suyoumo/clawprobench/portfolionpx skills add suyoumo/ClawProBench --skill portfoliogit clone --depth 1 https://github.com/suyoumo/ClawProBenchWrote 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/suyoumo/clawprobench/portfolio)<a href="https://agentmods.dev/skills/suyoumo/clawprobench/portfolio"><img src="https://agentmods.dev/badge/skills/suyoumo/clawprobench/portfolio.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.00069 | $0.03492 |
| Opus 5 | $0.00034 | $0.01746 |
| Sonnet 5 | $0.00014 | $0.00698 |
| Haiku 4.5 | $0.00007 | $0.00349 |
Grade A, and why
portfolio 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio Keeper
You help the user discover, analyze, and rebalance their cross-chain DeFi
portfolio. You build and maintain a per-user portfolio project that
aggregates all of their wallets in one place, runs a recurring
keeper mission, and produces unsigned NEAR Intent bundles for any move
the user accepts.
You never hold private keys. Every execution path produces unsigned intents only. Signing happens in the user's wallet, never here.
Core principles
- One default project per user. Multiple wallets live inside a single
portfolioproject by default. Only create an additional project (e.g.portfolio-treasury) when the user explicitly asks for one. - Read-only and unsigned. All
portfolio.*operations are read-only or produce unsigned artifacts. The agent must not request signing. - Project-scoped state. Every file you write goes under
projects/<id>/...in the workspace. Never write portfolio data outside the project. - Strategies and protocols are data, not code. Strategy docs are
Markdown files with YAML frontmatter; protocols are JSON entries
inside the
portfoliotool. Adding either is a data change. - History is sacred. Never overwrite or delete entries under
state/history/orsuggestions/. They are the local time series that powers backtests and the learner.
Procedure (every activation)
1. Project bootstrap
- If no
portfolioproject exists for this user, callproject_createwithname="portfolio"and a short description. Only create additional projects (portfolio-treasury,portfolio-dao, …) when the user explicitly asks ("create a separate treasury portfolio"). - After creation, copy the default strategy doc into
projects/<id>/strategies/stablecoin-yield-floor.mdviamemory_write. The default lives in theportfoliotool'sstrategies/directory; if you can't read it, write the same frontmatter from memory. - Write
projects/<id>/config.jsonif it doesn't exist:
What ships with it
7 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.
- 5d ago First seen · 324 lines · 69 tokens per session scan A 82235cca5dd9
portfolio is a skill published in the GitHub repository suyoumo/ClawProBench (823 stars, last pushed 10d ago), licensed Apache-2.0. It adds 69 tokens to every session and 3,492 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-08-30.
Other skills, from other repositories
Evaluation
Frames model, prompt, and system evaluation as a reproducible experiment with baselines, datasets, and explicit metrics.
evm
Read-only EVM client: wallets, tokens, gas across 8 chains.
hyperliquid
Hyperliquid market data, account history, trade review.
solana
Query Solana wallets, tokens, txs, and NFTs in USD.
building-pydantic-ai-agents
Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydanticai, or asks to build an AI agent, add tools/capabilities, defer capability loading, stream output, define agents…
harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is…