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 skills add rjmurillo/ai-agents --skill taste-lintsgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/taste-lints)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/taste-lints"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/taste-lints/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/skills/rjmurillo/ai-agents/taste-lints"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/taste-lints.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00972 |
| Opus 5 | $0.00023 | $0.00486 |
| Sonnet 5 | $0.00009 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
taste-lints 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 4d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taste Lints
Custom lints where error messages become agent-readable remediation instructions.
Inspired by OpenAI Harness Engineering:
"We statically enforce structured logging, naming conventions for schemas and types, file size limits, and platform-specific reliability requirements with custom lints. Because the lints are custom, we write the error messages to inject remediation instructions into agent context."
Triggers
| Trigger Phrase | Operation |
|---|---|
run taste lints |
taste_lints.py on staged or specified files |
check file size |
taste_lints.py with file-size rule only |
check naming conventions |
taste_lints.py with naming rule only |
lint taste invariants |
taste_lints.py full scan |
taste lint report |
taste_lints.py with JSON output |
When to Use
Use this skill when:
- Writing or editing source files (catch taste violations early)
- Preparing code for PR submission
- Reviewing code for style and convention compliance
- Adding new files to the project
Taste Invariants
1. File Size Limits
Files exceeding line thresholds indicate poor cohesion.
| Threshold | Lines | Severity |
|---|---|---|
| Warning | 301-500 | warning |
| Error | 501+ | error |
2. Naming Conventions
| Pattern | Rule | Applies To |
|---|---|---|
snake_case |
Python files, functions, variables | *.py |
kebab-case |
Skill directories, YAML files | .claude/skills/, *.yml |
PascalCase |
PowerShell functions, classes | *.ps1, *.psm1 |
UPPER_CASE |
Constants, environment variables | All languages |
invoke_ prefix |
Hook scripts | .claude/hooks/ |
3. Function Complexity
Functions exceeding cyclomatic complexity 10 need decomposition.
4. Skill Prompt Size
Skills exceeding 500 lines need progressive disclosure refactoring.
Process
- Run
python3 .claude/skills/taste-lints/scripts/taste_lints.pywith target files - Review AGENT_REMEDIATION blocks in output
- Apply suggested fixes
- Re-run to confirm compliance
What ships with it
1 file 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.
- 4d ago First seen · 126 lines · 47 tokens per session scan A 0c46db6851ed
taste-lints is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 972 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-09-03.
Other skills, from other repositories
loop-triage
Triage recent CI failures, open issues, and recent commits into a prioritized, actionable picture. Reads the prior STATE.md as memory and rewrites it. The maker half of the loop.
ci-triage
How to find out why a GitHub Actions run failed, and how to tell a real failure from a flake or an infrastructure problem. Use when a check is red, a workflow is stuck, or a run needs re-running.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
ci-cd
A guide for designing automated build and delivery workflows with GitHub Actions. These workflows can run checks such as tests, code-quality scans, coverage checks, and builds when code is pushed or a pull request is opened.
gha
Analyze GitHub Actions failures and identify root causes.
gitlab-pipeline-debugger
Debug and monitor GitLab CI/CD pipelines for merge requests. Check pipeline status, view job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitLab CI pipeline issues, check job statuses, or view specific job logs.