Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/anchildress1/awesome-github-copilot/eslint-plugin-configuringnpx skills add anchildress1/awesome-github-copilot --skill eslint-plugin-configuringgit clone --depth 1 https://github.com/anchildress1/awesome-github-copilotWrote 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/skills/anchildress1/awesome-github-copilot/eslint-plugin-configuring)<a href="https://agentmods.dev/skills/anchildress1/awesome-github-copilot/eslint-plugin-configuring"><img src="https://agentmods.dev/badge/skills/anchildress1/awesome-github-copilot/eslint-plugin-configuring.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 | $0.00037 | $0.01211 |
| Opus 5 | $0.00018 | $0.00606 |
| Sonnet 5 | $0.00007 | $0.00242 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
eslint-plugin-configs 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 5d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the agent responsible for creating or modifying an ESLint plugin package that exports:
rulesconfigs(flat and/or legacy)- optional
processors - recommended
meta(name,version,namespace)
Your output is plugin source code plus correct consumer usage examples.
This Skill targets ESLint v8.x and v9.x behavior explicitly.
Operating Assumptions
ESLint Version Semantics
-
ESLint v9
- Flat config is the default.
.eslintrc*is deprecated.- Legacy configs only apply if
ESLINT_USE_FLAT_CONFIG=false.
-
ESLint v8
.eslintrc*is the common default.- Flat config is opt-in via
eslint.config.jsorESLINT_USE_FLAT_CONFIG=true.
You must not misstate these behaviors.
Non-Goals (Hard Constraints)
- Do not claim the plugin can force configuration usage.
- Do not invent undocumented config resolution logic.
- Do not mix flat and legacy config shapes.
- Do not introduce ambiguous or colliding config names.
Required Inputs (Implicit)
Assume the following exist or are derivable:
PACKAGE_NAME(npm package name)NAMESPACE(rule/config prefix)RULES(map ofruleId -> rule implementation)- Optional desired config set (e.g.
recommended,strict)
Mandatory Plugin Shape
The plugin must export a single object with:
metanameversionnamespace
rulesconfigs- optional
processors
Preferred export is ESM default export.
Meta Rules
meta.namespaceis the canonical prefix for:- rules
- configs
- plugin registration
- All rule references must use
"<namespace>/<ruleId>". - Namespace consistency is mandatory across all outputs.
Config Export Strategies
Choose exactly one strategy and apply it consistently.
Strategy A — New Plugin (Recommended)
Use explicit separation:
- Flat configs:
flat/<configName> - Legacy configs:
legacy-<configName>
This avoids collisions and makes intent unambiguous.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 239 lines · 37 tokens per session scan A 06f7bb43c269
eslint-plugin-configs is a skill published in the GitHub repository anchildress1/awesome-github-copilot (65 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 1,211 once invoked, about $0.0002 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 skills, from other repositories
GitHub Copilot Testing Patterns
Effective patterns for using GitHub Copilot to generate, refactor, and maintain test code including prompt engineering for test generation, Copilot Chat for debugging, inline suggestions for assertions, and workspace context optimization.
mcp-server-dev
Use when the user asks to build an MCP server, create an MCP integration, wrap an API for AI agents, or expose tools via the Model Context Protocol. Guides through deployment model selection (remote HTTP, MCPB, local stdio), tool-design patterns, and framework choice before scaffolding code.
conventions-improver
Audit and improve project conventions files (AGENTS.md, CLAUDE.md, GEMINI.md). Scans for all conventions files, evaluates quality against a scoring rubric, outputs a quality report, then makes targeted improvements with user approval. Use when asked to check, audit, update, or improve AGENTS.md or similar files.
security-threat-model
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling.…
code-review
Multi-agent code review for local changes, files, or directories. Detects bugs, security issues, and conventions-file violations (AGENTS.md/CLAUDE.md/GEMINI.md).
comment-analyzer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Detects comment rot and misleading documentation. Use after adding or modifying code comments.