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.
npx agentmods add instructions/grodgers1-ctrl/kinky_link/agents-mdgit clone --depth 1 https://github.com/grodgers1-ctrl/kinky_linkWrote 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/grodgers1-ctrl/kinky_link/agents-md)<a href="https://agentmods.dev/instructions/grodgers1-ctrl/kinky_link/agents-md"><img src="https://agentmods.dev/badge/instructions/grodgers1-ctrl/kinky_link/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 | $0.00442 | $0.00442 |
| Opus 5 | $0.00221 | $0.00221 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
kinky_link 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.
What it actually says
This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
Auth + Supabase learnings
See auth-supabase-learnings.md for specific lessons about:
@auth/supabase-adapterschema behavior- PostgREST camelCase/snake_case pitfalls
- NextAuth v5 beta JWT callback patterns
- Route group vs URL path behavior
- Orphaned user cleanup
Brand: kinkylink
Brand assets and full guide at public/brand/kinkylink_brand.md.
Quick reference
- Primary: Placebo Sky
#ECFBFD - Secondary: Floppy Disk
#140044 - Accent: Red Flag
#FF224B - Surface: Off White
#EDEEEF - Text: Black
#000000 - Display font: Calibre Thin (48px)
- Body font: Calibre Light (16px)
- Logo:
public/brand/kinklink_logo.png - Tailwind theme vars:
--color-brand-{primary,secondary,accent,surface,text,white}
Code Review Self-Improvement
See code-review-learnings.md for lessons extracted from the Week 1 code review, covering:
- Security (service-role client, request validation)
- Error handling (try/catch, structured errors, UI feedback)
- TypeScript (NextAuth type extensions, no
any[]) - Next.js 16 conventions (NextRequest, async params)
- Brand consistency (UI primitives use brand tokens)
- UX states (loading, empty, error, inline edit feedback)
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 · 46 lines · 442 tokens per session scan A f681b4389281
kinky_link AGENTS.md is an instructions file published in the GitHub repository grodgers1-ctrl/kinky_link (0 stars, last pushed 1mo ago), licensed MIT. It adds 442 tokens to every session, about $0.0022 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.