Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/commands/pmdevsolutions/aurelius/lint)<a href="https://agentmods.dev/commands/pmdevsolutions/aurelius/lint"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/lint.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.1 | $0.00000 | $0.00313 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 yesterday.
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
Lint & Format
Run ESLint and Prettier across the project.
Purpose
This command checks and fixes code quality and formatting issues using ESLint and Prettier.
Usage
/lint
What this command does
- Runs ESLint to check for code quality issues
- Runs Prettier to check formatting
- Auto-fixes where possible
- Reports remaining issues that need manual attention
Steps
1. Check if tools are installed
pnpm eslint --version && pnpm prettier --version
2. Run ESLint with auto-fix
pnpm eslint . --fix --ext .ts,.tsx,.js,.jsx
3. Run Prettier
pnpm prettier --write "src/**/*.{ts,tsx,js,jsx,css,json,md}"
4. Type check
pnpm tsc --noEmit
Or use the project script
./scripts/lint-and-format.sh
Common Issues
- Missing ESLint config: Copy
templates/shared/eslint.config.jsto project root - Missing Prettier config: Copy
templates/shared/prettier.config.jsto project root - Conflicting rules: Ensure eslint-config-prettier is installed to disable formatting rules in ESLint
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.
- yesterday First seen · 55 lines · 0 tokens per session scan A 6b16b1cf649b
lint is a command published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 313 tokens. 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-04.
Other commands, from other repositories
figma-start
디자이너가 개발자의 원본 PR 위에서 검수를 시작할 때 호출하는 커맨드입니다. PR 링크 하나만 주면 프로젝트 클론부터 합니다 — 검수할 프로젝트를 미리 받아둘 필요가 없습니다. 브랜치 생성·체크아웃 후 빌드해서 기기에 올려 화면까지 띄워줍니다 — 실행할 기기·에뮬레이터가 없으면 검수에 맞는 걸 설치해서 만듭니다. 그 브랜치의 커밋 이력 패널도 개발툴에 띄워줍니다 — 지금까지 반영한 검수 내용을 검수 내내 옆에 두고 볼 수 있습니다. 커밋·푸시는 하지 않습니다. 디자이너가 화면을 먼저 확인한 뒤, 필요하면 /figma-apply로 피그마 변경을 반영합니다.
handoff
디자이너 작업 완료 신호 — design/ 브랜치로 dev 브랜치 타겟 PR을 만들고, 원본 dev PR 작성자를 리뷰어로 지정.
figma-apply
피그마 변경을 현재 design/ 브랜치에 반영(커밋·푸시). /figma-start 이후에 사용.
test
Run tests and ensure code quality for the Figma Console MCP server.
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
figma-component-library
Generate a complete component library in Figma from a design system config — atoms, molecules, and organisms with all variants, auto layout, and component properties.