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 instructions/charliedigital/runjs/general-codinggit clone --depth 1 https://github.com/CharlieDigital/runjsWhat 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.00527 | $0.00527 |
| Opus 5 | $0.00264 | $0.00264 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
runjs general-coding.instructions.md 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RunJS Project Overview
- This application is building an MCP server in C# and .NET 9 (C# version 13)
- You can use any C# features up to this version
- The Docker Hub image name is
cdigs/runjs-mcp-server; the username iscdigsand the repository isrunjs-mcp-server
Naming Conventions
- In .cs files, do not use
thisand prefer to use_prefix for private fields
C# (*.cs) Coding Style
- Prefer modern .NET conventions like primary constructors, collection initializers, var, record types, etc.
- Always use braces { } for control structures (if, for, while, etc.); do not leave them out even for single line statements
- When writing tests, use test function names like
MethodName_StateUnderTest_ExpectedBehaviorto clearly describe the test's purpose
Vue (*.vue) Coding Style
- Use defineModel, defineProps, and defineEmits macros where applicable
Commenting
- Add comments to explain logical decisions
- Document all function inputs
- Be descriptive with function comments
- When mentioning types, class names, etc in comments, use markdown backticks like
thisorMyClass
Structure
- The /app directory is a Nuxt 3 Vue web application which is using Quasar for the UI components
- The /cli directory contains a sample client application built with TypeScript and the Vercel AI SDK
- The /server directory contains the C# MCP server implementation
- The /tests directory contains integration tests using XUnit
Key Files
Logging
This codebase is using Serilog for logging. To create a logger for a class, use the following pattern:
// If it is a static class
private static readonly ILogger Log = Serilog.Log.ForContext(typeof(SomeStaticClass));
// If it is an instance class
private static readonly ILogger Log = Serilog.Log.ForContext<SomeInstanceClass>();
When logging, use the following pattern:
Log.Here().Information("This is an informational message with a parameter: {Parameter}", parameterValue);
Log.Here().Warning("This is a warning message with a parameter: {Parameter}", parameterValue);
Log.Here().Error(ex, "An error occurred with parameter: {Parameter}", parameterValue);
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 · 54 lines · 527 tokens per session scan A 08c3f65b59d4
runjs general-coding.instructions.md is an instructions file published in the GitHub repository CharlieDigital/runjs (31 stars, last pushed 1y ago), licensed MIT. It adds 527 tokens to every session, about $0.0026 per session on Opus 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-30.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.