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/m3sserstudi0s/swiparr/agents-mdgit clone --depth 1 https://github.com/m3sserstudi0s/swiparrWrote 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/m3sserstudi0s/swiparr/agents-md)<a href="https://agentmods.dev/instructions/m3sserstudi0s/swiparr/agents-md"><img src="https://agentmods.dev/badge/instructions/m3sserstudi0s/swiparr/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.01631 | $0.01631 |
| Opus 5 | $0.00816 | $0.00816 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
swiparr 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 6d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swiparr - Agent Development Guide
When you need to search docs, use context7 tools.
If you are unsure how to do something, use gh_grep to search code examples from GitHub.
Project Overview
Swiparr is a media discovery tool for Jellyfin, Emby, Plex, and TMDB, featuring a Tinder-like swipe interface.
- Framework: Next.js 16 (App Router), React 19 (React Compiler enabled)
- Styling: Tailwind CSS v4, Framer Motion
- Database: SQLite with Drizzle ORM
- State: Zustand (Global), TanStack Query (Server), React Hook Form (Forms)
- Auth: iron-session
Available Commands
Development & Building
npm run dev # Start dev server
npm run build # Run migrations and build for production
npm run lint # Run ESLint
Database Operations
npx drizzle-kit generate # Create migration from schema
npm run db:migrate # Apply migrations (uses tsx)
npx drizzle-kit push # Push schema directly (dev)
npx drizzle-kit studio # Database GUI
Testing
No test framework currently configured. Use standard Vitest/Jest patterns if adding.
Code Style Guidelines
Imports & Project Structure
- Path Aliases: Always use
@/*forsrc/*.import { db } from '@/db' import { Button } from '@/components/ui/button' - Grouping: 1. React/Next, 2. External libs, 3. Internal
@/*, 4. Local relative. - Exports: Prefer named exports for utilities/types; default exports for components/pages.
Naming Conventions
- Files:
kebab-case.ts(logic),PascalCase.tsx(components). - Components:
PascalCase. - Hooks:
useCamelCase. - Database: Tables are
PascalCasesingular in code, camelCase in DB. - API:
kebab-casefolder structure insrc/app/api/.
TypeScript & Types
- Strict Mode: Explicitly define return types for all exported functions.
- Drizzle Types:
export type User = InferSelectModel<typeof users> export type NewUser = InferInsertModel<typeof users> - Zod: Use for all external data validation (API requests, config).
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.
- 6d ago First seen · 120 lines · 1,631 tokens per session scan A f1a56fdd0765
swiparr AGENTS.md is an instructions file published in the GitHub repository m3sserstudi0s/swiparr (781 stars, last pushed 1mo ago), licensed MIT. It adds 1,631 tokens to every session, about $0.0082 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-30.
Other instructions, from other repositories
ARR_MCP AGENTS.md
Instructions for GauranshMathur/ARR_MCP, covering agents.md, non-negotiables, researching a service, adding a service and tool design.
ARR_MCP CLAUDE.md
Instructions for GauranshMathur/ARR_MCP, covering claude.md, build and run commands, code style guidelines, agent skills and issue tracker.
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).
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.
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.