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 Bilal140202/the-lord-of-the-skills --skill continuedev__continuegit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/continuedev__continue)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/continuedev__continue"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/continuedev__continue/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/bilal140202/the-lord-of-the-skills/continuedev__continue"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/continuedev__continue.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.00049 | $0.01329 |
| Opus 5 | $0.00024 | $0.00665 |
| Sonnet 5 | $0.00010 | $0.00266 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade A, and why
cn-check 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 9d 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.
This is a copy
100% identical to cn-check — 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cn check — Local AI Agent Checks
Run AI-powered code checks locally against your working tree changes using the Continue CLI. Each check is an agent (defined in markdown) that reviews your diff, identifies issues, and optionally suggests fixes as a patch.
When to Use
- User asks to run AI checks on their code changes
- User wants to set up
cn checkin a project - User needs to create custom check agents
- User wants to apply AI-suggested fixes locally
- User asks about Continue CI or agent-based code review
Installation
Prerequisites
- Node.js 18+
- A git repository with uncommitted or branched changes
Install the CLI
npm install -g @continuedev/cli
Authenticate (required for Hub checks, optional for local-only)
cn login
This opens a browser for authentication. After login, Hub-configured checks are available automatically.
Usage
Basic: Run all discovered checks
cn check
This auto-detects checks from three sources (in priority order):
- Hub API — checks configured for your repo on continue.dev
- Local agents — markdown files in
.continue/agents/*.md
Specify agents explicitly
# Run a single local agent
cn check --agent .continue/agents/security-review.md
# Run a Hub-published agent
cn check --agent myorg/code-style
# Run multiple agents
cn check --agent .continue/agents/security.md --agent .continue/agents/docs.md
Compare against a specific base branch
cn check --base develop
Default: auto-detects main or master.
Output formats
# JSON output (for CI pipelines or scripting)
cn check --format json
# Unified patch output (pipe to git apply)
cn check --patch | git apply
# Stop on first failure
cn check --fail-fast
Auto-fix mode
cn check --fix
Runs all checks, then applies any suggested patches directly to the working tree. Patches that conflict are reported but skipped.
Creating a Check Agent
Create a markdown file at .continue/agents/<name>.md:
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.
- 9d ago First seen · 201 lines · 49 tokens per session scan A 63d7241f9cc0
cn-check is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 1,329 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cn-check, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
codegraph
A local code-graph query tool for an existing project. It maps symbols and their relationships so you can search for definitions, callers, callees, affected files, and focused context.
analyze
Analyzes code quality, complexity, patterns across codebase. Triggers: quality report, hotspot scan, code analysis, architecture signal.
fact-checker
Anti-hallucination discipline for any code that names an external symbol you aren't certain exists — a library function, method, config key, package version, CLI flag, env var, or endpoint. Before you call it, cite it, or import it, confirm it's real: grep the codebase, read the installed package's actual signature…
ase-code-lint
Lint source code for potential code quality problems. Use when the user wants to "lint" or "check" source code.
deep-audit
Deep consistency audit of the entire repository infrastructure. Launches 4 parallel specialist agents to find factual errors, code bugs, count mismatches, and cross-document inconsistencies. Then fixes all issues and loops until clean. Use when: after making broad changes, before releases, or when user says "audit"…