Borrowing it
Nothing to install: this file belongs to gastonrey/licita-app. 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/gastonrey/licita-app/main/AGENTS.mdgit clone --depth 1 https://github.com/gastonrey/licita-appWrote 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/gastonrey/licita-app/agents-md)<a href="https://agentmods.dev/instructions/gastonrey/licita-app/agents-md"><img src="https://agentmods.dev/badge/instructions/gastonrey/licita-app/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.00940 | $0.00940 |
| Opus 5 | $0.00470 | $0.00470 |
| Sonnet 5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
licita-app 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 3d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Licita Project Guidelines
Product context
Licita is an agent-native public procurement intelligence product for professional teams. It indexes TED and, when enabled, PLACSP data to expose evidence-backed intelligence about tenders, buyers, suppliers, opportunities, and renewal signals through REST and MCP.
Primary users:
- Procurement and business-development professionals evaluating public-sector opportunities.
- AI-agent and integration developers consuming the REST/MCP surfaces.
- The operator monitoring acquisition, usage, revenue, and data quality.
The primary product outcome is helping a professional decide where to focus procurement activity next. Human-facing UX must lead with that decision value; protocol, payment, and implementation details are secondary.
Engineering conventions
- Runtime: Node.js 20+, TypeScript, ESM, Fastify, PostgreSQL, raw SQL, and Zod validation.
- Public web surfaces live in
src/web/; API routes live insrc/api/routes/; payments live insrc/pay/; migrations live inmigrations/; tests live intest/. - Preserve REST envelopes, MCP contracts, provenance, and explicit nulls. Never fabricate data.
- Validate untrusted input at the route boundary and enforce authorization server-side.
- Migrations are additive and replay-safe. Never modify production secrets or unrelated tooling files.
- Keep the public discovery surfaces stable:
/llms.txt,/openapi.json,/v1/pricing,/docs,/mcp, the MCP server card, use-case/data routes, and/robots.txt.
Commands
npm test
npm run test:integration
npm run test:api-smoke
npm run typecheck
npm run build
Local services:
docker compose up --build -d
docker compose logs -f app
Definition of done
- The user, primary job, decision, scope, and acceptance scenarios are explicit.
- Tests are written before implementation for new behavior (strict TDD).
npm test, relevant integration/smoke tests, typecheck, and build pass.- Error, empty, loading, success, and disabled states are covered.
- Security, privacy, authorization, and data-retention implications are reviewed.
- Public API, MCP, discovery, and provenance contracts have regression coverage.
- Documentation, deployment, and rollback notes are updated when applicable.
- No UI is considered complete without browser evidence or an explicit
Needs verificationdecision.
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.
- 3d ago First seen · 97 lines · 940 tokens per session scan A 93d8a56176fb
licita-app AGENTS.md is an instructions file published in the GitHub repository gastonrey/licita-app (0 stars, last pushed 4d ago), licensed MIT. It adds 940 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-09-04.
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.