Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rajitsaha/100xprismnpx agentmods add skills/rajitsaha/100xprism/lintWrote 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/rajitsaha/100xprism/lint)<a href="https://agentmods.dev/skills/rajitsaha/100xprism/lint"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/lint/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/rajitsaha/100xprism/lint"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/lint.svg" alt="Reviewed on agentmods" width="80" 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 Excessive Agency · line 7 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium MCP Rug Pull · line 46 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 51 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 60 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 65 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.00029 | $0.00954 |
| Opus 5.5 | $0.00012 | $0.00382 |
| Sonnet 5.5 | $0.00006 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00095 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint — Lint, Format & Type Check
You are a code quality engineer. Auto-detect the linting stack, run it, fix all errors. Zero errors before done.
Do NOT ask for permission — just fix everything.
Step 1 — Detect lint stack
PROJECT_ROOT=$(git rev-parse --show-toplevel)
cd "$PROJECT_ROOT"
ls pyproject.toml ruff.toml eslint.config.* .eslintrc* tsconfig.json 2>/dev/null
ls api/eslint.config.* api/.eslintrc* api/tsconfig.json 2>/dev/null
Determine which apply:
- ruff (Python):
pyproject.tomlwith[tool.ruff]section - ESLint (frontend):
eslint.config.*or.eslintrc*in root - ESLint (backend JS):
eslint.config.*or.eslintrc*inapi/ - TypeScript (frontend):
tsconfig.jsonin root - TypeScript (backend):
tsconfig.jsoninapi/
Step 2 — Auto-fix
ruff (Python):
./venv/bin/ruff check . --fix
./venv/bin/ruff format .
ESLint (frontend):
npm run lint -- --fix 2>/dev/null || npx eslint . --fix
ESLint (backend JS):
cd api && npm run lint -- --fix 2>/dev/null || npx eslint src --ext .ts --fix
Step 3 — Type check
TypeScript (frontend) — blocking:
npm run typecheck 2>&1 || npx tsc --noEmit 2>&1
TypeScript (backend JS) — blocking:
cd api && npm run typecheck 2>&1 || npx tsc --noEmit 2>&1
Python mypy — non-blocking:
./venv/bin/mypy . --ignore-missing-imports 2>&1 || true
Step 4 — Fix remaining errors manually
For each error auto-fix could not handle, read the file and fix it.
ESLint:
no-unused-vars/@typescript-eslint/no-unused-vars→ remove or prefix with_@typescript-eslint/no-explicit-any→ replace with proper type orunknownno-console→ replace with project loggerreact-hooks/exhaustive-deps→ add missing deps or wrap withuseCallback/useMemo@typescript-eslint/no-non-null-assertion→ add null check instead of!
TypeScript:
TS2339(property does not exist) → add to type or use optional chainingTS2345(type mismatch) → fix type or cast with justificationTS2304(cannot find name) → add importTS7006(implicit any) → add explicit type annotation
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.
- 1mo ago First seen · 127 lines · 29 tokens per session scan A 614f6f609975
lint is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 13d ago), licensed MIT. It adds 29 tokens to every session and 954 once invoked, about $0.0001 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 skills, from other repositories
clean-code-reviewer
Reviews code against Robert C. Martin's Clean Code principles. Use when users share code for review, ask for refactoring suggestions, or want to improve code quality. Produces actionable feedback organized by Clean Code principles with concrete before/after examples.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
skill-creator
Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.