Borrowing it
Nothing to install: this file belongs to Sartori-RIA/ubuteco_api. 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/Sartori-RIA/ubuteco_api/master/AGENTS.mdgit clone --depth 1 https://github.com/Sartori-RIA/ubuteco_apiWrote 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/sartori-ria/ubuteco_api/agents-md)<a href="https://agentmods.dev/instructions/sartori-ria/ubuteco_api/agents-md"><img src="https://agentmods.dev/badge/instructions/sartori-ria/ubuteco_api/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.01239 | $0.01239 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
ubuteco_api 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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — ubuteco_api
Instructions for AI assistants working in this repository.
Also: CLAUDE.md (Claude Code) · .github/copilot-instructions.md (GitHub Copilot) — both point here.
Stack
- Ruby 4 / Rails 8.1 API-only
- PostgreSQL, Redis, Sidekiq, Searchkick + OpenSearch, AnyCable
- Auth: Devise + JWT (
allowlisted_jwts) - Authorization: CanCanCan
- Money: money-rails (amounts as cents + ISO currency columns)
Active frontend
ubuteco-react is the only active UI. Angular ubuteco_spa is abandoned — do not port or reference it.
Before you code
- Read docs/plans/README.md — pick one plan, check status and dependencies.
- Read docs/workflow-plans-and-git.md — small commits, update plan before PR (canonical for all agents; not only Cursor).
- Read docs/context/common-ai-pitfalls.md — frequent agent mistakes in this repo.
- Small API bugs / polish: docs/backlog/README.md — promote to a plan if scope grows.
- Read docs/context/architecture.md for tenant model and request flow.
- Read domain context for your plan area — see Key paths.
- Read docs/dev-setup.md for ports and local commands.
Branching
- Implementation (code): one plan = one branch —
feature/<plan-slug>(e.g.feature/locale-and-currency). Do not mix unrelated plans on the same branch. - Plan docs (
docs/plans/, status checkboxes, new plan files): commit directly onmaster— no feature branch or PR required. - Backlog docs (
docs/backlog/): commit directly onmasterwhen text-only. - Other docs-only (context, ADRs, dev-setup): also fine on
master, ordocs/<topic>if you prefer a short-lived branch.
Plans, commits & PRs
Read docs/workflow-plans-and-git.md before opening a PR.
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.
- 8d ago First seen · 85 lines · 1,239 tokens per session scan A 166a2b0397f9
ubuteco_api AGENTS.md is an instructions file published in the GitHub repository Sartori-RIA/ubuteco_api (10 stars, last pushed 2mo ago), licensed MIT. It adds 1,239 tokens to every session, about $0.0062 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).
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).
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.
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.