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 rules/verdikta/verdikta-applications/bounty-program-architecturegit clone --depth 1 https://github.com/verdikta/verdikta-applicationsWrote 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/rules/verdikta/verdikta-applications/bounty-program-architecture)<a href="https://agentmods.dev/rules/verdikta/verdikta-applications/bounty-program-architecture"><img src="https://agentmods.dev/badge/rules/verdikta/verdikta-applications/bounty-program-architecture.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.00000 | $0.01184 |
| Opus 5 | $0.00000 | $0.00592 |
| Sonnet 5 | $0.00000 | $0.00237 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
bounty-program-architecture 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 6d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bounty Program Architecture
Project Structure
Backend (Server)
- server.js - Main Express server
- utils/archiveGenerator.js - Creates Verdikta-compatible archives
- utils/jobStorage.js - Local job database (temporary until smart contracts)
- routes/jobRoutes.js - Job management API endpoints
- data/jobs.json - Local job storage
Frontend (Client)
- pages/CreateBounty.jsx - Job creation UI
- pages/Home.jsx - Job browsing/search
- pages/BountyDetails.jsx - Job details view
- pages/SubmitWork.jsx - Work submission UI
- services/api.js - API service layer
Key Concepts
Multi-CID Architecture
The system generates two types of IPFS archives:
-
Primary CID Archive: Contains evaluation instructions
manifest.json- Jury config, rubric reference, hunter CID referenceprimary_query.json- Evaluation instructions and outcomes
-
Hunter CID Archive: Contains work submission
manifest.json- Work product file references with descriptionsprimary_query.json- Submission narrative (customizable by hunter)submission/- Directory with actual work product files
Threshold Separation
IMPORTANT: The threshold is NOT stored in the rubric JSON on IPFS. It is:
- Stored separately in job records (currently in jobs.json)
- Will be stored on-chain in smart contracts
- This allows same rubric to be reused with different thresholds
Archive Generation Pattern
// Create Primary archive
const primaryArchive = await archiveGenerator.createPrimaryCIDArchive({
rubricCid,
jobTitle,
jobDescription,
workProductType,
classId,
juryNodes,
iterations,
hunterSubmissionCid // References Hunter archive
});
// Create Hunter archive
const hunterArchive = await archiveGenerator.createHunterSubmissionCIDArchive({
workProducts: [
{ path, name, type, description }
],
submissionNarrative // Custom message to evaluators
});
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.
- 6d ago First seen · 138 lines · 0 tokens per session scan A fde9d0de5e35
bounty-program-architecture is a cursor rule published in the GitHub repository verdikta/verdikta-applications (24 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,184 tokens. 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.