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 instructions/stakemate369/yieldsignal/claude-mdgit clone --depth 1 https://github.com/Stakemate369/yieldsignalWrote 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/instructions/stakemate369/yieldsignal/claude-md)<a href="https://agentmods.dev/instructions/stakemate369/yieldsignal/claude-md"><img src="https://agentmods.dev/badge/instructions/stakemate369/yieldsignal/claude-md.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.08102 | $0.08102 |
| Opus 5 | $0.04051 | $0.04051 |
| Sonnet 5 | $0.01620 | $0.01620 |
| Haiku 4.5 | $0.00810 | $0.00810 |
Grade A, and why
yieldsignal CLAUDE.md 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Commands
npm install # instala dependências
npm test # roda toda a suíte (vitest run)
npm run test:watch # vitest em modo watch
npx tsc --noEmit # typecheck sem gerar arquivos — rodar depois de qualquer mudança
npm run signal # calcula e imprime o sinal AGORA, com dados reais — sem servidor, sem carteira, sem credencial CDP nenhuma (USDC por padrão; `npm run signal -- WETH` pro outro ativo)
npm run dev # sobe o servidor x402 (lê X402_ENVIRONMENT do .env pra decidir development/production)
npm run test:paid # cria uma carteira compradora de teste, pega USDC de teste no faucet da CDP, e faz uma chamada paga de verdade contra localhost:4021 — só funciona em development
npm run withdraw # saca o USDC acumulado pra OWNER_WALLET_ADDRESS — pede confirmação manual digitada "CONFIRM"
npm run register-schema # registra o schema EAS uma única vez (mainnet, gasta gas real) — pede "CONFIRM"
npm run attest # publica UMA atestação on-chain do sinal atual (mainnet, gasta gas real) — pede "CONFIRM"
npm run register-agent # mint único de identidade ERC-8004 (mainnet, gasta gas real) — pede "CONFIRM"
npm run bazaar:check # compara o preço anunciado no índice do Bazaar com o que cada rota cobra hoje — não gasta nada
npm run bazaar:sync # paga UMA chamada real em cada rota divergente pra reescrever o preço no índice (gasta USDC da carteira compradora)
npm run fund-buyer -- 1.50 # devolve USDC da receptora pra compradora, pra manutenção nunca precisar de aporte externo
Manutenção paga é um CICLO FECHADO — nunca peça aporte novo
As chamadas de bazaar:sync saem da carteira COMPRADORA e caem na RECEPTORA, as duas do dono: o dinheiro troca de bolso, não é gasto. Quando a compradora seca, o valor está na receptora — a resposta certa é npm run fund-buyer, não pedir depósito. Só existe custo real se a receptora também estiver vazia.
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 · 171 lines · 8,102 tokens per session scan A ba3867022806
yieldsignal CLAUDE.md is an instructions file published in the GitHub repository Stakemate369/yieldsignal (0 stars, last pushed 26d ago), licensed MIT. It adds 8,102 tokens to every session, about $0.0405 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.