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/morajabi/yc-partner/agents-mdgit clone --depth 1 https://github.com/morajabi/yc-partnerWrote 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/morajabi/yc-partner/agents-md)<a href="https://agentmods.dev/instructions/morajabi/yc-partner/agents-md"><img src="https://agentmods.dev/badge/instructions/morajabi/yc-partner/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.02397 | $0.02397 |
| Opus 5 | $0.01198 | $0.01198 |
| Sonnet 5 | $0.00479 | $0.00479 |
| Haiku 4.5 | $0.00240 | $0.00240 |
Grade A, and why
yc-partner 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 4d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Source Of Truth
The root README.md is the product source of truth. If lower-level scaffolding disagrees with it, update the skill and repo structure to match the README.
Goal
yc-partner is a public, open source knowledge pack and agent skill for founders applying to Y Combinator.
It should help users:
- Answer pre-application YC questions and doubts before they finish writing.
- Review YC applications with fresh eyes.
- Improve clarity, specificity, and application hygiene.
- Estimate whether the application is likely to earn an interview.
- Prepare for YC interviews.
- Verify advice against YC resources, YC-affiliated material, examples, and founder stories.
- Find relevant YC resources to read or watch.
Skill Boundary
The skill is the artifact. skills/yc-partner/SKILL.md is for founders using the installed skill, not for maintainers building the corpus.
Keep runtime skill instructions focused on:
- How to answer pre-application questions and doubts.
- How to review applications.
- How to prepare founders for interviews.
- What sources to trust.
- How to find bundled resources.
- Tone, posture, required vs optional behavior, and dos/don'ts.
Keep collection, transcription, scraping, indexing, and guide-generation instructions outside the runtime skill, in AGENTS.md, README.md, scripts/README.md, or maintainer docs.
Public-Safe Boundary
Do not include:
- Private YC applications unless explicitly contributed for public use.
- Personal contact information, private founder profiles, emails, phone numbers, screenshots, internal notes, or unpublished drafts.
- Private anecdotes unless rewritten as approved public examples.
- Secrets, credentials,
.envfiles, auth cookies, browser session data, or private API outputs. - Raw unprocessed HTML, downloaded videos, audio files, screenshots, caption JSON, or temporary scraper outputs.
If a file contains private information or application-specific content, keep it out of yc-partner.
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.
- 4d ago First seen · 187 lines · 2,397 tokens per session scan A 6f1ab928213c
yc-partner AGENTS.md is an instructions file published in the GitHub repository morajabi/yc-partner (5 stars, last pushed 2mo ago), licensed MIT. It adds 2,397 tokens to every session, about $0.0120 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.