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 Cypsy1714/cchad --skill javascript-skillgit clone --depth 1 https://github.com/Cypsy1714/cchadWrote 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/cypsy1714/cchad/javascript-skill)<a href="https://agentmods.dev/skills/cypsy1714/cchad/javascript-skill"><img src="https://agentmods.dev/badge/skills/cypsy1714/cchad/javascript-skill/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/cypsy1714/cchad/javascript-skill"><img src="https://agentmods.dev/badge/skills/cypsy1714/cchad/javascript-skill.svg" alt="Reviewed on agentmods" width="80" 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.00224 |
| Opus 5.5 | $0.00008 | $0.00090 |
| Sonnet 5.5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
javascript-conventions 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.
What it actually says
JavaScript conventions
Language
- Use
constby default,letwhen you must reassign, nevervar. - Use
===/!==; avoid the coercing==. - Prefer
async/awaitover raw promise chains, and always handle rejections. - Use ES modules (
import/export), not CommonJS, in new code.
Data
- Favor immutable transforms —
map,filter,reduce, spread — over mutating loops. - Use optional chaining (
?.) and nullish coalescing (??) instead of long&&guards or||that swallows0/"". - Destructure to name what you use.
Structure
- Small, pure functions where possible; isolate side effects.
- Fail fast with early returns instead of deep nesting.
- Throw
Errorobjects (not strings) and add context to the message.
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 · 24 lines · 19 tokens per session scan A 6c33756f4b25
javascript-conventions is a skill published in the GitHub repository Cypsy1714/cchad (1 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 224 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
daily-workflow
Daily development workflow for Symfony projects including common tasks, debugging, and productivity tips.
unity-coder
Use when implementing Unity C# code to follow proper coding guidelines, naming conventions, member ordering, and Unity-specific patterns.
python-coder
Implements Python code following PEP 8, type hints, and project conventions. Use when implementing features designed by python-architect.
python-testing
Python testing patterns with pytest including unit tests, integration tests, fixtures, mocking, and coverage. Use when writing Python tests.
typescript-coder
Implements TypeScript/JavaScript code following established architecture and coding guidelines. Use when implementing features designed by typescript-architect.
typescript-testing
TypeScript testing patterns with Jest/Vitest including unit tests, integration tests, mocking strategies, and coverage. Use when writing TypeScript tests.