Borrowing it
Nothing to install: this file belongs to Nimbleway/agent-skills. 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/Nimbleway/agent-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/Nimbleway/agent-skillsWrote 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/nimbleway/agent-skills/claude-md)<a href="https://agentmods.dev/instructions/nimbleway/agent-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/nimbleway/agent-skills/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.04740 | $0.04740 |
| Opus 5 | $0.02370 | $0.02370 |
| Sonnet 5 | $0.00948 | $0.00948 |
| Haiku 4.5 | $0.00474 | $0.00474 |
Grade B, and why
agent-skills CLAUDE.md scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
export NIMBLE_API_KEY="your-key" # or set in ~/.claude/settings.json under env How it starts
The opening of the file, as written. The whole thing — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
What this repo is
Nimble Web Search Skills — agent skills that give any AI agent the ability to search, scrape, and extract structured data from any website using the Nimble CLI. Built following the Agent Skills specification, compatible with Claude Code, Codex, Cursor, and any agent platform that supports the spec.
Two layers of skills:
- Core data skill (
skills/nimble-web-expert/) — the raw capabilities: fetch a URL, run a search, map/crawl a site, run Extraction Templates, and run Web Search Agents - Business intelligence skills (every other skill) — one-command workflows that turn live web data into actionable reports
See .claude-plugin/marketplace.json for the full list of published skills.
Business skills are built on top of the core skill — they call nimble search / nimble extract, run Extraction Templates for structured site data, and run Web Search Agents for open-ended research, under the hood.
Prerequisites
npm i -g @nimble-way/nimble-cli
export NIMBLE_API_KEY="your-key" # or set in ~/.claude/settings.json under env
Repo structure
skills/
{skill-name}/ # Each skill is a DIRECT child of skills/
SKILL.md # Skill definition (frontmatter + instructions)
references/ # On-demand docs, loaded when needed (reference.md, never SKILL.md)
agents/ # Shared sub-agent definitions (.md with frontmatter)
_shared/ # Canonical shared references (synced into skills)
assets/ # Plugin listing assets (logo, composer icon)
.claude-plugin/plugin.json # Claude Code plugin manifest
.cursor-plugin/plugin.json # Cursor plugin manifest
.codex-plugin/plugin.json # OpenAI / Codex plugin manifest
.grok-plugin/plugin.json # xAI / Grok Build plugin manifest
plugin.json # Portable Agent Plugins manifest
.mcp.json # Hosted MCP config — Claude Code Connector + Codex (Grok inline)
mcp.json # Portable Agent Plugins MCP config (different vocabulary)
commands/ # Slash commands
scripts/ # Repo tooling
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.
- 8d ago First seen · 358 lines · 4,740 tokens per session scan B c995d093f884
agent-skills CLAUDE.md is an instructions file published in the GitHub repository Nimbleway/agent-skills (53 stars, last pushed 12d ago), licensed MIT. It adds 4,740 tokens to every session, about $0.0237 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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).
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.