Borrowing it
Nothing to install: this file belongs to richard-gyiko/data-wrangler-plugin. 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/richard-gyiko/data-wrangler-plugin/main/AGENTS.mdgit clone --depth 1 https://github.com/richard-gyiko/data-wrangler-pluginWrote 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/richard-gyiko/data-wrangler-plugin/agents-md)<a href="https://agentmods.dev/instructions/richard-gyiko/data-wrangler-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/richard-gyiko/data-wrangler-plugin/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/richard-gyiko/data-wrangler-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/richard-gyiko/data-wrangler-plugin/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.00469 | $0.00469 |
| Opus 5.5 | $0.00188 | $0.00188 |
| Sonnet 5.5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
data-wrangler-plugin 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 2mo 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.
What it actually says
Agent Guidelines
Skill Best Practices
While working on a skill or planning a new spec to extend or modify the skill, make sure to follow the skill best practices here
Development Workflow
Follow this workflow when creating or modifying skills:
1. Create Specs
- Define the feature requirements and scope
- Document expected behavior and edge cases
- Read best practices before finalizing specs
2. Create Implementation Plan
- Break down the work into actionable steps
- Identify files to create or modify
- Use Context7 tools to fetch up-to-date library/SDK documentation for any libraries being used
- Read best practices and verify the plan aligns with them
3. Cross-Check Specs and Implementation Plan
- Verify the plan covers all spec requirements
- Ensure nothing is missed or over-engineered
- Confirm alignment with best practices (conciseness, progressive disclosure, etc.)
4. Implement
- Follow the implementation plan step by step
- Keep changes minimal and focused
5. Validate Against Best Practices
- Review implementation against best practices
- Check for: conciseness, appropriate freedom levels, consistent terminology
- Ensure progressive disclosure patterns are used correctly
6. Cross-Check Implementation with Plan
- Verify all planned items are implemented
- Confirm no scope creep or missing pieces
7. Create Tests
- Write meaningful, valuable tests that cover:
- Core functionality
- Edge cases from specs
- Error handling
8. Run Tests and Fix Issues
- Execute all tests
- Fix any failures
- Re-run until all tests pass
Key Principle
Always consult best practices during planning phases. Before finalizing specs or implementation plans, read through claude_skills_best_practices.md to ensure alignment with:
- Conciseness guidelines
- Progressive disclosure patterns
- Workflow and feedback loop recommendations
- Template and examples patterns
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.
- 2mo ago First seen · 57 lines · 469 tokens per session scan A 105861b356df
data-wrangler-plugin AGENTS.md is an instructions file published in the GitHub repository richard-gyiko/data-wrangler-plugin (3 stars, last pushed 10mo ago), licensed MIT. It adds 469 tokens to every session, about $0.0019 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.