Oficina AGENTS.md

A starting guide for coding agents working with Oficina, a NestJS and TypeScript project pattern that uses Prisma and PostgreSQL. It points agents to rules and task-specific guides for areas such as database schemas, permissions, and CRUD features.

In plain words
What is it for?
Use it as the entry point for Oficina-based work, then consult the matching guide for CRUD modules, database migrations, access control, task breakdowns, documentation, or agent workflow.
Why use it?
It helps agents find the relevant project conventions before changing code, data models, security rules, or client-facing documents.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/joaoequer/oficina/agents-md
Clone the repo
git clone --depth 1 https://github.com/JoaoEquer/Oficina

Made for: Codex, OpenCode.

Per session 335 This file is loaded in full into every session.
When invoked 335 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00335 $0.00335
Opus 5 $0.00168 $0.00168
Sonnet 5 $0.00067 $0.00067
Haiku 4.5 $0.00034 $0.00034

Measured 2d ago against content hash 81c8f4dc4ba4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Oficina 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 2d 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.

AGENTS.md · 22 lines

What it actually says

AGENTS.md — Oficina

Entry point for harnesses that read AGENTS.md (Codex, Cursor, OpenCode, Gemini CLI and similar).

This repository is a lean harness of working patterns for the NestJS + TypeScript + Prisma + PostgreSQL stack.

When working on any project that references this harness:

  1. Follow the always-on rules in rules/:
    • rules/engineering-philosophy.md — how the team decides (pragmatism, no over-engineering)
    • rules/git-workflow.md — branches, commits, documentation from day 0
    • rules/security-baseline.md — security and multi-tenancy non-negotiables
    • rules/agent-workflow.md — how to direct the agent itself (plan before code, scoped sessions, early correction)
  2. Consult the skills in skills/ before executing tasks in the covered areas:
    • nestjs-crud-pattern — creating any CRUD module/domain/route
    • prisma-schema-conventions — creating/changing schema, planning migrations
    • rbac-design — permissions, roles, access control
    • clickup-task-breakdown — breaking scope into tasks
    • client-facing-docs — any material the client will read
    • token-efficiency — session setup, token/context limits, RTK
  3. Documentary source of truth: data model and scope come from the project's documents. Divergence is a blocker to resolve with the tech lead, not a detail to ignore.
Changes

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.

  1. 2d ago First seen · 22 lines · 335 tokens per session scan A 81c8f4dc4ba4

Subscribe to this mod's changes

Oficina AGENTS.md is an instructions file published in the GitHub repository JoaoEquer/Oficina (2 stars, last pushed 1mo ago), licensed MIT. It adds 335 tokens to every session, about $0.0017 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.

Related

Other instructions, from other repositories

ReqForge CLAUDE.md

Instructions for zxpmail/ReqForge, a project described as: ReqForge — From requirements to shippable products. Open-source Agent Harness for Claude Code, Cursor & OpenCode. Spec→Plan→Build, hooks, review. /change-manager for brownfield.

zxpmail/ReqForge · 1,753 tokens

prisma-class-generator CLAUDE.md

Instructions for kimjbstar/prisma-class-generator, covering claude.md, what this is, architecture, commands and testing approach.

kimjbstar/prisma-class-generator · 2,495 tokens

ai-harness CLAUDE.md

Instructions for samartomar/ai-harness, covering ai-harness — claude bootloader, vocabulary — two different things, read the source, not a summary of it, start here and self-hosting boundary.

samartomar/ai-harness · 1,290 tokens

StateCore CLAUDE.md

Claude Code instructions for yul761/StateCore, covering statecore — claude context, what this is, commands, running locally and enable semantic retrieval (optional).

yul761/StateCore · 2,688 tokens

ai-harness AGENTS.md

Instructions for samartomar/ai-harness, covering ai-harness — agent bootloader (agents.md), start here, self-hosting boundary, working agreement and invariants.

samartomar/ai-harness · 891 tokens

RepoResident AGENTS.md

Instructions for ychamel/RepoResident: Agent entry point: read CLAUDE.md in full — it is the operating manual — then follow its Session protocol. Everything else (state, workflows, project knowledge) is routed from there via the .agent/ directory.

ychamel/RepoResident · 50 tokens