Borrowing it
Nothing to install: this file belongs to koreyba/Claude-Skill-pdf-to-epub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/koreyba/Claude-Skill-pdf-to-epub/master/AGENTS.mdgit clone --depth 1 https://github.com/koreyba/Claude-Skill-pdf-to-epubWrote 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/koreyba/claude-skill-pdf-to-epub/agents-md)<a href="https://agentmods.dev/instructions/koreyba/claude-skill-pdf-to-epub/agents-md"><img src="https://agentmods.dev/badge/instructions/koreyba/claude-skill-pdf-to-epub/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.
<a href="https://agentmods.dev/instructions/koreyba/claude-skill-pdf-to-epub/agents-md"><img src="https://agentmods.dev/badge/instructions/koreyba/claude-skill-pdf-to-epub/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00486 | $0.00486 |
| Opus 5 | $0.00243 | $0.00243 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
Claude-Skill-pdf-to-epub 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 11d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI DevKit Rules
Project Context
This project uses ai-devkit for structured AI-assisted development. Phase documentation is located in docs/ai/.
Documentation Structure
docs/ai/requirements/- Problem understanding and requirementsdocs/ai/design/- System architecture and design decisions (include mermaid diagrams)docs/ai/planning/- Task breakdown and project planningdocs/ai/implementation/- Implementation guides and notesdocs/ai/testing/- Testing strategy and test casesdocs/ai/deployment/- Deployment and infrastructure docsdocs/ai/monitoring/- Monitoring and observability setup
Code Style & Standards
- Follow the project's established code style and conventions
- Write clear, self-documenting code with meaningful variable names
- Add comments for complex logic or non-obvious decisions
Development Workflow
- Review phase documentation in
docs/ai/before implementing features - Keep requirements, design, and implementation docs updated as the project evolves
- Reference the planning doc for task breakdown and priorities
- Copy the testing template (
docs/ai/testing/README.md) before creating feature-specific testing docs
AI Interaction Guidelines
- When implementing features, first check relevant phase documentation
- For new features, start with requirements clarification
- Update phase docs when significant changes or decisions are made
Testing & Quality
- Write tests alongside implementation
- Follow the testing strategy defined in
docs/ai/testing/ - Use
/writing-testto generate unit and integration tests targeting 100% coverage - Ensure code passes all tests before considering it complete
Documentation
- Update phase documentation when requirements or design changes
- Keep inline code comments focused and relevant
- Document architectural decisions and their rationale
- Use mermaid diagrams for any architectural or data-flow visuals (update existing diagrams if needed)
- Record test coverage results and outstanding gaps in
docs/ai/testing/
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.
- 11d ago First seen · 51 lines · 486 tokens per session scan A c50e87bd5da6
Claude-Skill-pdf-to-epub AGENTS.md is an instructions file published in the GitHub repository koreyba/Claude-Skill-pdf-to-epub (33 stars, last pushed 7mo ago), licensed MIT. It adds 486 tokens to every session, about $0.0024 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
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.
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.
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).
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.