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 arbazkhan971/godmode --skill lintgit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/lint)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/lint"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/lint.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, 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 34 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]
- medium MCP Rug Pull · line 97 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]
- medium MCP Rug Pull · line 98 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]
- medium MCP Rug Pull · line 107 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]
- medium MCP Rug Pull · line 108 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.00075 | $0.01731 |
| Opus 5 | $0.00037 | $0.00865 |
| Sonnet 5 | $0.00015 | $0.00346 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
lint 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint — Linting & Code Standards
Activate When
- User invokes
/godmode:lint - User says "set up linting", "fix code style"
- User asks about ESLint, Prettier, Biome, Ruff
- Codebase has inconsistent formatting
- Migrating between linting tools
Workflow
Step 1: Assess Current State
# Detect existing configurations
ls -la .eslintrc* .prettierrc* biome.json \
.editorconfig .stylelintrc* .golangci.yml \
pyproject.toml .flake8 .rubocop.yml 2>/dev/null
# Check for pre-commit hooks
ls .husky/ .pre-commit-config.yaml 2>/dev/null
# Count current violations
npx eslint . --format compact 2>/dev/null | wc -l
ruff check . --statistics 2>/dev/null
LINT ASSESSMENT:
Language(s): <detected>
| Aspect | Status |
|--------------|----------------------|
| Linter | <tool or NONE> |
| Formatter | <tool or NONE> |
| Pre-commit | YES/NO |
| Editor config| YES/NO |
| Violations | <N errors, N warns> |
| CI enforce | YES/NO |
IF no linter: install recommended for language
IF no formatter: add Prettier/Biome/gofmt
IF no hooks: set up Husky + lint-staged
IF warnings > 0 in CI: set --max-warnings=0
Step 2: Tool Selection
TOOL SELECTION:
| Language | Linter | Formatter |
|------------|---------------|---------------|
| TypeScript | ESLint/Biome | Prettier/Biome|
| Python | Ruff | Ruff/Black |
| Go | golangci-lint | gofmt |
| Rust | clippy | rustfmt |
| Ruby | RuboCop | RuboCop |
| CSS/SCSS | Stylelint | Prettier |
IF project has ESLint+Prettier: consider Biome
IF Python with flake8+black: migrate to Ruff
Step 3: Configuration
ESLint 9+ flat config with typescript-eslint, prettier.
Biome: single biome.json for lint+format+imports.
Ruff: pyproject.toml [tool.ruff] section.
Go: .golangci.yml with 5m timeout.
Step 4: Auto-Fix Strategy
AUTO-FIX LAYERS:
Level 1: Format on Save (editor, zero effort)
Level 2: Lint Fix on Save (safe rules only)
Level 3: Pre-commit (staged files, catches misses)
Level 4: CI Enforcement (final gate, no auto-fix)
THRESHOLDS:
Batch fix target: resolve 100% of auto-fixable
Manual remaining: list with file:line for user
IF auto-fix changes semantics: DISCARD fix
IF false positive rate > 20%: disable rule
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 · 212 lines · 75 tokens per session scan A 496bdb54db6f
lint is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 10d ago), licensed MIT. It adds 75 tokens to every session and 1,731 once invoked, about $0.0004 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
agent-design-best-practices
Best practices for designing Claude Code agent files (.claude/agents/.md). This skill should be used when writing or reviewing agent markdown files to ensure proper design with focused domains, correct tool access, reusable definitions, and separation of capabilities from lifecycle. Combines Anthropic's official…
referee
Final arbiter for Bug Hunter. Receives Hunter findings and Skeptic challenges, independently re-reads code, and delivers authoritative verdicts with CVSS scoring and proof-of-concept generation for security findings.
om-merge-buddy
Scan open pull requests via the configured tracker, classify merge readiness from labels, reviews, CI, and mergeability, then report which PRs can merge now and which ones are close but blocked.
ralph-specum-feedback
This skill should be used only when the user explicitly asks to use $ralph-specum-feedback, or explicitly asks Ralph Specum in Codex to draft or submit feedback.
auditor-quiz
Quiz an auditor on a codebase's mechanics and vulnerabilities, drawn from its own code and docs. Use to test understanding before or during a review.
testing-strategy
Design test strategies and test plans with coverage targets. Complements /draft:coverage which measures what this skill plans. Auto-loaded by /draft:implement before TDD.