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.
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/electron-angular-native)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/electron-angular-native"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/electron-angular-native/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/agents/kimiski33/awesome-copilot/electron-angular-native"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/electron-angular-native.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.00051 | $0.01903 |
| Opus 5.5 | $0.00020 | $0.00761 |
| Sonnet 5.5 | $0.00010 | $0.00381 |
| Haiku 4.5 | $0.00005 | $0.00190 |
Grade A, and why
Electron Code Review Mode Instructions 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Use safe wrappers (child_process with `spawn` not `exec` for large data) This is a copy
100% identical to Electron Code Review Mode Instructions — 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electron Code Review Mode Instructions
You're reviewing an Electron-based desktop app with:
- Main Process: Node.js (Electron Main)
- Renderer Process: Angular (Electron Renderer)
- Integration: Native integration layer (e.g., AppleScript, shell, or other tooling)
Code Conventions
- Node.js: camelCase variables/functions, PascalCase classes
- Angular: PascalCase Components/Directives, camelCase methods/variables
- Avoid magic strings/numbers — use constants or env vars
- Strict async/await — avoid
.then(),.Result,.Wait(), or callback mixing - Manage nullable types explicitly
Electron Main Process (Node.js)
Architecture & Separation of Concerns
- Controller logic delegates to services — no business logic inside Electron IPC event listeners
- Use Dependency Injection (InversifyJS or similar)
- One clear entry point — index.ts or main.ts
Async/Await & Error Handling
- No missing
awaiton async calls - No unhandled promise rejections — always
.catch()ortry/catch - Wrap native calls (e.g., exiftool, AppleScript, shell commands) with robust error handling (timeout, invalid output, exit code checks)
- Use safe wrappers (child_process with
spawnnotexecfor large data)
Exception Handling
- Catch and log uncaught exceptions (
process.on('uncaughtException')) - Catch unhandled promise rejections (
process.on('unhandledRejection')) - Graceful process exit on fatal errors
- Prevent renderer-originated IPC from crashing main
Security
- Enable context isolation
- Disable remote module
- Sanitize all IPC messages from renderer
- Never expose sensitive file system access to renderer
- Validate all file paths
- Avoid shell injection / unsafe AppleScript execution
- Harden access to system resources
Memory & Resource Management
- Prevent memory leaks in long-running services
- Release resources after heavy operations (Streams, exiftool, child processes)
- Clean up temp files and folders
- Monitor memory usage (heap, native memory)
- Handle multiple windows safely (avoid window leaks)
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 · 287 lines · 51 tokens per session scan A 61e624aa3aa3
Electron Code Review Mode Instructions is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,903 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). It is 100% identical to Electron Code Review Mode Instructions, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…