llm-safe-sql: Instructions file for Codex

AGENTS.md

llm-safe-sql AGENTS.md is an instructions file for Codex, OpenCode from hyuga611/llm-safe-sql. It costs 758 tokens per session, scanned A, original, MIT.

Repository instructions for developers and coding agents working on llm-safe-sql, a library that measures proposed SQL data changes and then rolls them back.

In plain words
What is it for?
Guiding work on llm-safe-sql, including tests for MySQL and PostgreSQL behaviour and protection against data-loss bugs.
Why use it?
They document safety rules and database behaviours that contributors must check before changing or declaring the project complete.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is hyuga611/llm-safe-sql's own configuration. It tells Codex and OpenCode how to work on llm-safe-sql itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything llm-safe-sql configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hyuga611/llm-safe-sql. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hyuga611/llm-safe-sql/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/hyuga611/llm-safe-sql

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for llm-safe-sql AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hyuga611/llm-safe-sql/agents-md/github.svg)](https://agentmods.dev/instructions/hyuga611/llm-safe-sql/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/hyuga611/llm-safe-sql/agents-md"><img src="https://agentmods.dev/badge/instructions/hyuga611/llm-safe-sql/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for llm-safe-sql AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hyuga611/llm-safe-sql/agents-md"><img src="https://agentmods.dev/badge/instructions/hyuga611/llm-safe-sql/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 758 This file is loaded in full into every session.
When invoked 758 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00758 $0.00758
Opus 5.5 $0.00303 $0.00303
Sonnet 5.5 $0.00152 $0.00152
Haiku 4.5 $0.00076 $0.00076

Measured 2mo ago against content hash b24793b13256, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

llm-safe-sql 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 2mo 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 · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Notes for coding agents

If you are an LLM working on this repository, read this first. It is short.

What this project is

A library that lets a language model propose an UPDATE or DELETE, executes it inside a transaction to measure what it really does, always rolls back, and shows a human the measurement to approve. You are, in a sense, the adversary this is written for — so hold yourself to the standard the code holds its caller to.

Rules that are not style preferences

Never weaken a refusal to make a test pass. If a case is refused and you believe it should not be, the fix is to prove the case can be handled correctly and add a test that shows it. Removing the check because it is in the way reintroduces a data-loss bug that somebody found the hard way.

Never assume a database behaviour — measure it. Rules marked 🔬 in SPEC.md were established by running MySQL 8.4 and PostgreSQL 16 and observing the result. Twice the documentation was wrong and the measurement won. If your change depends on engine behaviour, add a test to test/integration/semantics.test.ts that would fail if a future version changed its mind. Do not cite documentation in a comment as if it were evidence.

Do not delete a comment because it looks redundant. Nearly every non-obvious line here exists because something specific went wrong, and the comment is the only record of what. If you change the line, update the comment to explain your version; if the reason is genuinely gone, say so in the commit message.

A refusal must name the right problem. UPDATE order SET … was once refused as an ORDER BY, which sent the operator to fix something unrelated. Detect clauses by position, not by whether a word appears.

False alarms are defects. A conflict check that fires when another team edited an unrelated column, or a rollback verifier that reports failure because someone else committed, is worse than not having the check — people switch off tools that lie to them. If you add a check, write the test that shows it stays quiet in the innocent case.

Read the full file on GitHub · 65 lines

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. 2mo ago First seen · 65 lines · 758 tokens per session scan A b24793b13256

Subscribe to this mod's changes

llm-safe-sql AGENTS.md is an instructions file published in the GitHub repository hyuga611/llm-safe-sql (0 stars, last pushed 2mo ago), licensed MIT. It adds 758 tokens to every session, about $0.0030 per session on Opus 5.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

llm-safe-sql AGENTS.md compared with instructions from other repositories

llm-safe-sql AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
llm-safe-sql AGENTS.mdhyuga611/llm-safe-sqlInstructions file02mo agoMITA758Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode