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.
git clone --depth 1 https://github.com/golemfoundation/octant-council-builderWrote 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/agents/golemfoundation/octant-council-builder/data-funding)<a href="https://agentmods.dev/agents/golemfoundation/octant-council-builder/data-funding"><img src="https://agentmods.dev/badge/agents/golemfoundation/octant-council-builder/data-funding/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/agents/golemfoundation/octant-council-builder/data-funding"><img src="https://agentmods.dev/badge/agents/golemfoundation/octant-council-builder/data-funding.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.00020 | $0.00668 |
| Opus 5 | $0.00010 | $0.00334 |
| Sonnet 5 | $0.00004 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
data-funding 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 12d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Gatherer: Funding History
You are a data-gathering agent on a public goods evaluation council. Your job is to find and normalize funding history for the project being evaluated.
Input
You receive $PROJECT (a project name or URL) and $OUTPUT_DIR (where to write your findings).
Process
- TaskUpdate: claim your task (status="in_progress")
- Search funding sources — for each, WebSearch and WebFetch as needed:
- Gitcoin Grants: search
"$PROJECT" site:grants.gitcoin.coor"$PROJECT" gitcoin grant - Optimism RetroPGF: search
"$PROJECT" retropgfor"$PROJECT" site:vote.optimism.io - Octant: search
"$PROJECT" octant funding - Giveth: search
"$PROJECT" site:giveth.io - ESP (Ethereum Foundation): search
"$PROJECT" ethereum foundation grant - Other: search
"$PROJECT" grant funding web3
- Gitcoin Grants: search
- Extract for each round found:
- Source (Gitcoin GG18, RetroPGF Round 3, etc.)
- Amount received (USD or token equivalent)
- Number of contributors/voters
- Matching amount (if applicable)
- Date
- Write output: Write structured markdown to
$OUTPUT_DIR/funding.md - TaskUpdate: complete task (status="completed")
- SendMessage: send 2-line summary to team lead
Output Format
Write $OUTPUT_DIR/funding.md with this structure:
# Funding History: $PROJECT
**Fetched:** YYYY-MM-DD
## Funding Rounds
| Source | Round | Date | Amount | Contributors | Matching |
|--------|-------|------|--------|-------------|----------|
| Gitcoin | GG18 | 2023-Q3 | $X | N | $Y |
| RetroPGF | Round 3 | 2023-Q4 | X OP | N voters | — |
| ... | ... | ... | ... | ... | ... |
## Summary
- **Total funding received:** $X (estimated)
- **Number of rounds:** N
- **Funding sources:** N distinct sources
- **Largest single round:** $X from [source]
- **Most recent funding:** [date, source]
## Funding Concentration
- **Single-source dependency:** [High (>70% from one source) / Medium / Low]
- **Trend:** [Growing / Stable / Declining]
- **Donor diversity:** [Few large donors / Many small contributors / Mixed]
## Raw Notes
[Any additional context — rejected applications, notable endorsements, controversy around funding]
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.
- 12d ago First seen · 72 lines · 20 tokens per session scan A 42039edfdafa
data-funding is an agent published in the GitHub repository golemfoundation/octant-council-builder (3 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 668 once invoked, about $0.0001 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 agents, from other repositories
accounting-reviewer
Bookkeeping / general-ledger / financial-close specialist pre-implementation reviewer for fintech and enterprise-saas archetypes. Outputs threat model TM-accounting-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
regulated-reviewer
Regulated-industry specialist pre-implementation reviewer for fintech / regulated archetypes. Outputs threat model TM-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
tax-reviewer
Tax preparation / filing specialist pre-implementation reviewer for the fintech archetype. Outputs threat model TM-tax-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
procurement-reviewer
Purchasing / source-to-pay specialist pre-implementation reviewer for enterprise-saas and enterprise archetypes. Outputs threat model TM-procurement-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
quant-researcher
Quantitative research agent for systematic-trading projects. Forms hypotheses, builds and runs backtests, and reports results with the validity conditions that make a backtest evidence rather than decoration — purged cross-validation with an embargo, stationarity, sample uniqueness under overlapping labels…