Borrowing it
Nothing to install: this file belongs to aget-framework/aget. 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/aget-framework/aget/main/.claude/skills/aget-lint-code/SKILL.mdgit clone --depth 1 https://github.com/aget-framework/agetWrote 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/aget-framework/aget/aget-lint-code)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-lint-code"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-lint-code/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/aget-framework/aget/aget-lint-code"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-lint-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 50 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00012 | $0.00578 |
| Opus 5.5 | $0.00005 | $0.00231 |
| Sonnet 5.5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
aget-lint-code 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 1mo 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
aget-lint-code
Run code linting and formatting checks on files or directories. Auto-detects linter configuration and reports issues by severity.
Instructions
When this skill is invoked:
-
Detect Linter Configuration
- Python: ruff, flake8, pylint (pyproject.toml, setup.cfg)
- JavaScript: eslint (.eslintrc.*)
- Go: golangci-lint (.golangci.yml)
- YAML: yamllint
-
Execute Linter
- Use project configuration
- Target specified files or all
- Capture output
-
Process Results
- Categorize by severity (error, warning, info)
- Extract file locations
- Count issues
-
Report Findings
- Summary by severity
- Issue details with locations
- Fix suggestions if available
Execution Commands
# Python (ruff)
ruff check [path] --output-format=text
# Python (flake8)
flake8 [path]
# JavaScript (eslint)
npx eslint [path] --format stylish
# Go
golangci-lint run [path]
# YAML
yamllint [path]
Output Format
## Lint Results
### Summary
| Severity | Count |
|----------|-------|
| Errors | [N] |
| Warnings | [N] |
| Info | [N] |
| **Total** | [N] |
### Status: [CLEAN/ISSUES FOUND]
### Issues by File
#### [filename.py]
| Line | Severity | Rule | Message |
|------|----------|------|---------|
| [N] | Error | [E001] | [Description] |
| [N] | Warning | [W002] | [Description] |
### Auto-fixable
[N] issues can be auto-fixed with `--fix` flag.
### Recommended Actions
1. [Fix critical errors first]
2. [Address warnings]
Constraints
- C1: NEVER apply auto-fixes without explicit --fix flag — lint is read-only by default
- C2: NEVER ignore configuration files — project configuration must be respected
- C3: NEVER fail silently when linter is misconfigured — configuration errors must be surfaced
Related
- SKILL-023: aget-lint-code specification
- ONTOLOGY_developer.yaml: Code, Code_Change concepts
- CAP-DEV-002: Code Linting capability
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.
- 1mo ago First seen · 105 lines · 12 tokens per session scan A 1a31a296a107
aget-lint-code is a skill published in the GitHub repository aget-framework/aget (12 stars, last pushed 7d ago), licensed Apache-2.0. It adds 12 tokens to every session and 578 once invoked, about $0.0000 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-30.
Other skills, from other repositories
aget-check-health
Run AGET health inspection and housekeeping checks. Detect-only — pair with /aget-enhance-health for remediation.
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual mandate — spec coverage audit plus deep bug finding, asking what breaks in the field and which assumptions are wrong. Superseded by /aget-check-release.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818) — coverage and consistency mode, asking whether a spec covers all behaviors and where gaps or contradictions remain. Superseded by /aget-check-release.
aget-release-build
Execute release gate deliverables with the Builder perspective of the Release Delivery Triad (L818) — speed-optimized execution asking whether the work is done, fast, and functional. Superseded by /aget-create-release.
aget-file-issue
File issues with L520 governance compliance.