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/ariadoss/superskills/bencium-code-conventionsnpx skills add ariadoss/superskills --skill bencium-code-conventionsgit clone --depth 1 https://github.com/ariadoss/superskillsWrote 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/ariadoss/superskills/bencium-code-conventions)<a href="https://agentmods.dev/skills/ariadoss/superskills/bencium-code-conventions"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/bencium-code-conventions.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.00019 | $0.00728 |
| Opus 5 | $0.00010 | $0.00364 |
| Sonnet 5 | $0.00004 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
bencium-code-conventions scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Test APIs via curl commands first, then implement in code This is a copy
100% identical to bencium-code-conventions — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Conventions
Core Technologies
- Frontend: ReactJS, Next.js (App Router structure), TypeScript
- Styling: TailwindCSS v3.x (never v4), Shadcn UI
- Build Tools: Vite (when applicable)
- Backend: Postgres compatible convex.dev or Supabase (always ask, never local postgres)
- Deployment: Netlify or Vercel or Fly - suggest
- Environment: Mac M2, Python3 with virtual environments, no CUDA, no Docker
- Alternative Languages: Avoid python if you can, try using RUST
Code Style & Structure
- Use ES modules (import/export) syntax
- Destructure imports when possible
- Use TypeScript for all new code
- Use async/await instead of Promise chains
- Prefer const/let over var; use early returns
- Use consts instead of functions:
const toggle = () =>. Define types. - Use descriptive variable names with auxiliary verbs (e.g.,
isLoading,hasError) - Use lowercase with dashes for directory names (e.g.,
components/auth-wizard)
Framework Conventions
- Next.js: Use App Router (app directory) structure and page.tsx files
- React: Functional and declarative patterns; avoid classes
- State Management: Zustand, TanStack React Query
- Validation: Zod for schema validation
Component Library & Styling
- Component Library: Prefer shadcn components from
@/components/ui - Styling: Tailwind utility classes
- Layout: Grid/flex wrappers with
gapfor spacing - Icons:
@phosphor-icons/react - Toasts:
sonnerfor notifications - Always add loading states, spinners, placeholder animations
Quality Assurance & Testing
- TDD: Write failing tests first, commit them, then iterate until suite passes
- Never mock tests - if there's a test script, execute all until done
- Always write SQL in chunks with test steps after each chunk
- Typecheck after making code changes
- Run tests before committing
- Prefer running single tests for performance, not whole suite
Error Handling
- Implement proper error handling and user input validation
- Error messages should be understood by non-technical people
- Use early returns for error conditions
- Test APIs via curl commands first, then implement in code
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.
- 6d ago First seen · 75 lines · 19 tokens per session scan A 0d330a7d5fe8
bencium-code-conventions is a skill published in the GitHub repository ariadoss/superskills (9 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 728 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to bencium-code-conventions, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…