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 agentmods add skills/jy315189/everything-cursor/coding-standardsnpx skills add jy315189/everything-cursor --skill coding-standardsgit clone --depth 1 https://github.com/jy315189/everything-cursorWhat 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 | $0.00000 | $0.02045 |
| Opus 5 | $0.00000 | $0.01022 |
| Sonnet 5 | $0.00000 | $0.00409 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
coding-standards 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 2d 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards Skill
Enforced code quality standards and patterns for production TypeScript/JavaScript projects.
When to Use
This skill is always relevant when writing or reviewing code. It defines the non-negotiable quality baseline.
1. Core Principles
Immutability — NEVER Mutate
// ❌ MUTATION — causes hidden bugs, breaks React rendering, ruins debugging
const users = [{ id: 1, name: 'Alice' }]
users.push({ id: 2, name: 'Bob' }) // mutates array
users[0].name = 'Alicia' // mutates object
// ✅ IMMUTABLE — predictable, traceable, safe
const added = [...users, { id: 2, name: 'Bob' }]
const updated = users.map(u => u.id === 1 ? { ...u, name: 'Alicia' } : u)
const removed = users.filter(u => u.id !== 1)
// For deep updates, use structured spread or immer:
const deepUpdate = {
...state,
user: {
...state.user,
address: { ...state.user.address, city: 'New York' }
}
}
Single Responsibility — One Reason to Change
// ❌ GOD FUNCTION: validates, transforms, persists, notifies
async function handleUserRegistration(req: Request) {
// 80+ lines doing everything...
}
// ✅ DECOMPOSED: each function does one thing
async function handleUserRegistration(req: Request) {
const input = validateRegistrationInput(req.body) // validate
const user = await createUser(input) // persist
await sendWelcomeEmail(user.email) // notify
return formatUserResponse(user) // transform
}
2. Naming Conventions
Variables and Functions
// Boolean: use is/has/can/should prefix — reads like English
const isActive = true
const hasPermission = user.role === 'admin'
const canEdit = hasPermission && !isLocked
const shouldRetry = attempts < MAX_RETRIES
// Functions: verb + noun — describes the action
function getUserById(id: string): Promise<User> {}
function calculateOrderTotal(items: OrderItem[]): number {}
function formatCurrency(amount: number, locale: string): string {}
// Event handlers: handle + Event
function handleSubmit(event: FormEvent) {}
function handleUserCreated(user: User) {}
// Avoid: vague names, abbreviations, single letters (except loops)
// ❌ data, info, temp, val, res, cb, fn, idx
// ✅ userData, connectionInfo, temporaryToken, responseBody
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.
- 2d ago First seen · 321 lines · 0 tokens per session scan A 479a3bd85e4c
coding-standards is a skill published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,045 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…