Borrowing it
Nothing to install: this file belongs to appydave/appydave-tools. 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/appydave/appydave-tools/main/AGENTS.mdgit clone --depth 1 https://github.com/appydave/appydave-toolsWrote 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/appydave/appydave-tools/agents-md)<a href="https://agentmods.dev/instructions/appydave/appydave-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/appydave/appydave-tools/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.01031 | $0.01031 |
| Opus 5 | $0.00515 | $0.00515 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
appydave-tools 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 yesterday.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Core Ruby code lives in lib/appydave/tools/ with one folder per CLI (gpt_context, youtube_manager, subtitle_processor, etc.). Executables in bin/ are for development helpers, while packaged entrypoints reside in exe/. Specs mirror the library layout under spec/, supported by sample data in spec/samples/. Shared docs and walkthroughs are collected under docs/. Temporary or generated artifacts (coverage/, tmp/, transient/) should stay out of commits.
Build, Test, and Development Commands
bin/setup installs gem dependencies and any Node helpers declared in package.json. Run bundle exec rake spec (aliased as rake spec) for the full test suite, and keep guard running during feature work to auto-rerun specs. Use bundle exec rubocop to enforce lint rules, and bin/console for an interactive Pry session preloaded with the gem. CLI binaries can be invoked directly, e.g., bin/gpt_context.rb -i '**/*.rb' -d.
Coding Style & Naming Conventions
The codebase targets Ruby 2.7 with two-space indentation and descriptive method names. Follow .rubocop.yml: 200-character line limit, relaxed metrics inside spec/, and RuboCop RSpec/Rake plugins enabled. Namespaces follow AppyDave::Tools::<Feature> inside lib/, and CLI filenames stay snake_case (bin/move_images.rb). Prefer keyword args, early returns, and guard clauses over deeply nested conditionals.
Testing Guidelines
RSpec is the canonical framework. Name files *_spec.rb that mirror lib paths (e.g., spec/gpt_context/collector_spec.rb). Isolate behavior with describe '#method' blocks, keep helpers in spec/support, and favor let/let! over global state. Run focused tests via bundle exec rspec spec/path/to/file_spec.rb when iterating, then finish with rake spec. Add regression tests for every bug fix to keep CLI behavior stable.
Commit & Pull Request Guidelines
Commits follow conventional commits consumed by semantic-release (feat:, fix:, chore:, feat!:, etc.). Scope messages to a single tool when possible (fix(subtitle_processor): correct offset buffer). Before opening a PR, ensure rake spec and rubocop pass, summarize the change, link issues or YouTube scripts, and include CLI output or screenshots if user-facing behavior shifts. Leave follow-up tasks in checklists so reviewers can track outstanding work.
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.
- yesterday First seen · 66 lines · 1,031 tokens per session scan A eeaff81313a6
appydave-tools AGENTS.md is an instructions file published in the GitHub repository appydave/appydave-tools (9 stars, last pushed 1mo ago), licensed MIT. It adds 1,031 tokens to every session, about $0.0052 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-09-05.
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).
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.
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.