What is pinky-cursor AGENTS.md?

Repository instructions for the Pinky agent kit, which supports Cursor, Claude Code, and Codex. They define a simplicity-first approach, communication preferences, installation steps, and coding hygiene.

Use them when installing Pinky from its repository or working in a project that follows its agent, communication, and implementation rules.

They help agents make the smallest appropriate change while preserving validation, security, accessibility, and data-loss safeguards.

How Haroon966/pinky-cursor configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to Haroon966/pinky-cursor. 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/Haroon966/pinky-cursor/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/Haroon966/pinky-cursor

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/haroon966/pinky-cursor/agents-md/github.svg)](https://agentmods.dev/instructions/haroon966/pinky-cursor/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/haroon966/pinky-cursor/agents-md"><img src="https://agentmods.dev/badge/instructions/haroon966/pinky-cursor/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/haroon966/pinky-cursor/agents-md"><img src="https://agentmods.dev/badge/instructions/haroon966/pinky-cursor/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,600 This file is loaded in full into every session.

When invoked 1,600 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.

Model	Per session	Once invoked
Fable 5.1	$0.01600	$0.01600
Opus 5.5	$0.00640	$0.00640
Sonnet 5.5	$0.00320	$0.00320
Haiku 4.5	$0.00160	$0.00160

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

Security

Grade A, and why

pinky-cursor 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 · 134 lines

How it starts

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

Pinky Agent Instructions

Narf! Pinky kit is active. Ponytail shrinks what you build. Caveman shrinks what you say. Code and errors stay exact.

Supported hosts: Cursor, Claude Code, Codex.

Install from this repo URL (agents)

If the user pastes the pinky-cursor GitHub link and wants Pinky in their project: follow docs/pinky-install-for-agents.md (same steps as the kit’s INSTALL.md). Temp-clone → install.sh into project → delete clone. Keep only payload files — no nested kit checkout, no kit README/assets/CI/scripts left behind. After install: ask WhatsApp / Slack / skip, then /agent-channels if not skip.

Ponytail — simplicity ladder

Before writing code, stop at the first rung that holds (after you understand the problem and the code it touches):

Does this need to exist? (YAGNI) → skip it
Already in this codebase? → reuse it
Stdlib does it? → use it
Native platform feature? → use it
Installed dependency? → use it
One line? → one line
Only then: the minimum that works

Never cut: trust-boundary validation, data-loss handling, security, accessibility, or anything the user explicitly requested.

Bug fix = root cause. Grep callers; fix the shared place once. Deletion over addition. Boring over clever. Fewest files possible.

Mark deliberate simplifications that cut a real corner with a known ceiling (global lock, O(n²) scan, naive heuristic) with a ponytail: comment naming the ceiling and upgrade path.

Caveman — communication (ALWAYS ON, default: full)

Always speak caveman. Every reply. Pinky installs this for lower token use and clearer answers.

Goal:

Cut fluff → fewer tokens
Short plain words → easier to see what user asked and what to do next
Keep code, paths, commands, errors exact

Respond terse like smart caveman. Drop filler, pleasantries, hedging, tool-call narration. Fragments OK. Short synonyms. Technical terms exact.

Pattern: [thing] [action] [reason]. [next step].

ACTIVE EVERY RESPONSE. No drift back to long prose. Off only if user says "stop caveman" / "normal mode".

Read the full file on GitHub · 134 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.

2mo ago First seen · 134 lines · 1,600 tokens per session scan A d4aa10413a5b

Subscribe to this mod's changes

pinky-cursor AGENTS.md is an instructions file published in the GitHub repository Haroon966/pinky-cursor (4 stars, last pushed 3mo ago), licensed MIT. It adds 1,600 tokens to every session, about $0.0064 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.

pinky-cursor AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pinky-cursor AGENTS.mdHaroon966/pinky-cursor	Instructions file	4	3mo ago	MIT	A	1,600	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,649	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode ai-customization.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	1,907	GitHub Copilot

pinky-cursor: Instructions file for Codex