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/cliffagius/spinaprize.net/agents-mdgit clone --depth 1 https://github.com/CliffAgius/Spinaprize.netWrote 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/cliffagius/spinaprize.net/agents-md)<a href="https://agentmods.dev/instructions/cliffagius/spinaprize.net/agents-md"><img src="https://agentmods.dev/badge/instructions/cliffagius/spinaprize.net/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 | $0.00963 | $0.00963 |
| Opus 5 | $0.00481 | $0.00481 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
Spinaprize.net 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 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions
Project overview
Spinaprize.net is a .NET 10 Blazor Web App for meetup prize draws. It lets organizers create an in-memory event, configure prizes and sponsors, share attendee entry links/codes, run a display-friendly draw wheel, reveal winners, export a manager report, and close the event.
Repository layout
Spinaprize.slnxis the solution entry point.src/Spinaprize.Webcontains the Blazor Web App.src/Spinaprize.Web/Components/Pagescontains routeable Razor pages for the organizer, attendee, wheel, winner, and report flows.src/Spinaprize.Web/Servicescontains app services.SpinaprizeEventServiceis the singleton in-memory event store for the MVP.src/Spinaprize.Web/Modelscontains request, event, prize, attendee, winner, and wheel display models.tests/Spinaprize.Web.Testscontains xUnit tests for core event behavior.docs/screenshotsstores existing UI screenshots; do not regenerate or replace them unless the task asks for screenshot updates.
Environment and commands
- Use the .NET SDK requested by
global.json(10.0.301,rollForward: latestFeature). - Restore/build the solution with
dotnet restore Spinaprize.slnxanddotnet build Spinaprize.slnx. - Run tests with
dotnet test Spinaprize.slnx. - Run the app locally with
dotnet run --project src/Spinaprize.Web.
Coding guidance
- Preserve nullable reference types and implicit usings.
- Follow the existing minimal-hosting Blazor pattern in
Program.cs. - Keep the MVP data model in memory unless the task explicitly asks for persistence.
- Keep organizer-only access flows tied to
ManagerAccessStateand manager-key validation. - Maintain the projection-friendly, accessible UI: high contrast, large controls, keyboard focus states, and reduced-motion behavior.
- Prefer small, testable service/model changes over embedding business logic directly in Razor components.
- Add or update xUnit coverage in
tests/Spinaprize.Web.Testswhen changing event rules, attendee registration, prize drawing, reporting, or manager access behavior.
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 · 64 lines · 963 tokens per session scan A b90fdd5c8ef1
Spinaprize.net AGENTS.md is an instructions file published in the GitHub repository CliffAgius/Spinaprize.net (5 stars, last pushed 1mo ago), licensed MIT. It adds 963 tokens to every session, about $0.0048 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
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.
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).
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.
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).