Borrowing it
Nothing to install: this file belongs to verdikta/verdikta-applications. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/verdikta/verdikta-applications/main/AGENTS.mdgit 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/instructions/verdikta/verdikta-applications/agents-md)<a href="https://agentmods.dev/instructions/verdikta/verdikta-applications/agents-md"><img src="https://agentmods.dev/badge/instructions/verdikta/verdikta-applications/agents-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.00930 | $0.00930 |
| Opus 5 | $0.00465 | $0.00465 |
| Sonnet 5 | $0.00186 | $0.00186 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
verdikta-applications AGENTS.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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Verdikta Applications
Read this file before changing code, documentation, issues, or Project metadata for this repository. Human contributors should follow the same backlog rules.
Repository ownership
verdikta-applications owns reference and production-facing application work,
including the bounty escrow, bounty API and UI, dashboards, indexers, example
frontends, and integration examples.
Protocol aggregation belongs in verdikta-dispatcher; arbiter-node behavior in
verdikta-arbiter; shared schemas and ClassID data in verdikta-common; and
agent-runtime behavior in verdikta-agents. Cross-repository outcomes use a
roadmap parent and repository-owned native sub-issues.
Verdikta backlog workflow (mandatory)
- Project: Verdikta Master Backlog
- Canonical guide: Backlog and issue workflow
Repository issues are the source of truth for work. The Project provides shared Status, Readiness, Priority, Size, Area, and roadmap progress. Never create a duplicate issue just to make work visible in the Project.
Navigate the backlog
- Top Priorities answers what Verdikta should work on next.
- Agent Queue shows
Ready+Todowork, but is not automatic permission to execute it. - Execution Board tracks active work by Status.
- Blocked shows work requiring intervention.
- Roadmap shows cross-repository initiatives and child progress.
- Master Backlog is the complete inventory.
Before starting work
- Read the full issue, its parent initiative, dependencies, linked PRs, and repository instructions.
- Search this repository and the organization for duplicates or superseding work.
- Confirm the issue is in the Master Backlog and is owned by this repository.
- Confirm
Readiness = Ready. If scope, acceptance criteria, validation, or a decision is missing, keep or setNeeds Triageand resolve the gap instead of guessing. - Confirm the requested action, permissions, and risk make autonomous work appropriate. Agent Queue membership alone is insufficient.
- Assign the implementing GitHub identity when practical and set
Status = In Progressonly when work actually begins.
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.
- 7d ago First seen · 108 lines · 930 tokens per session scan A 79b52053e798
verdikta-applications AGENTS.md is an instructions file published in the GitHub repository verdikta/verdikta-applications (24 stars, last pushed 3d ago), licensed MIT. It adds 930 tokens to every session, about $0.0047 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 instructions, from other repositories
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 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).
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.
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.