Borrowing it
Nothing to install: this file belongs to Delibread0601/askaipods. 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/Delibread0601/askaipods/main/CLAUDE.mdgit clone --depth 1 https://github.com/Delibread0601/askaipodsWrote 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/delibread0601/askaipods/claude-md)<a href="https://agentmods.dev/instructions/delibread0601/askaipods/claude-md"><img src="https://agentmods.dev/badge/instructions/delibread0601/askaipods/claude-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.00817 | $0.00817 |
| Opus 5 | $0.00409 | $0.00409 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
askaipods CLAUDE.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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
askaipods — project instructions
A zero-dependency npm CLI (askaipods) and companion agentskills.io skill that wraps the podlens.net semantic search API, returning recent quote excerpts from AI podcasts. Distributed as a global CLI via npx / npm install and as a skill drop-in under each runtime's skills/ directory (~/.claude/skills/, ~/.codex/skills/, ~/.openclaw/skills/ or ~/.agents/skills/, ~/.hermes/skills/). README holds the authoritative per-runtime path table.
Release notes style
GitHub release notes describe what changed, not how the change was arrived at. Do not mention Codex quality review rounds (R1, R2, ...), plugin-dev:skill-reviewer passes, /verify scans, /code-audit iterations, model identifiers, rejected-finding references, round counts, or "quality gates passed" sections. Include: features, fixes, contract changes, user-facing string changes, breaking changes, honest limitations, migration notes, and deferred scope for the next release (named in plain English, without review artifacts).
Release notes are written for npm / GitHub consumers, not for internal project history. The v0.2.3 and v0.2.4 release notes are the cleanest style templates.
This rule applies to the GitHub release body only — not to git commit messages (where referencing the review process for internal repo history is fine) and not to internal review transcripts.
Release workflow
- Bump the version in three locations (all three must match, every time):
package.json"version"src/cli.jsconst VERSION = "..."src/client.jsUser-Agentheader string
- Commit and push to
main. The.github/workflows/auto-tag.ymlworkflow watchespackage.jsonchanges onmain; when the version field changes and the tag does not already exist, it creates and pushes thevX.Y.Ztag. It does not create a GitHub release. - Create the GitHub release manually with
gh release create vX.Y.Z --title "vX.Y.Z — <short descriptor>" --notes "$(cat <<'EOF' ... EOF)", following the §Release notes style rule above. Usegh release editto amend; do not delete-and-recreate (URLs break, subscribers re-notified). - Publish to npm (
npm publish) if the release is a source change — skip npm publish for release-note-only corrections.
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 · 34 lines · 817 tokens per session scan A 29ec20785497
askaipods CLAUDE.md is an instructions file published in the GitHub repository Delibread0601/askaipods (2 stars, last pushed 4mo ago), licensed MIT. It adds 817 tokens to every session, about $0.0041 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
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.