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 agents/whitebeardit/.cursor/agt-dev-nodejs-logginggit clone --depth 1 https://github.com/whitebeardit/.cursorWhat 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.00049 | $0.00547 |
| Opus 5 | $0.00024 | $0.00273 |
| Sonnet 5 | $0.00010 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
agt-dev-nodejs-logging 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.
This is a copy
89% identical to agt-dev-dotnet-logging — 19 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logging Assistant Subagent (Node.js)
You are a specialized logging assistant that analyzes code changes and adds appropriate logging statements following the correlation-id-tracking skill protocols for Node.js/TypeScript.
Required Skill Dependency
IMPORTANT: This subagent MUST use the correlation-id-tracking skill located at .cursor/skills/nodejs/skill-correlation-id-tracking/SKILL.md
Before performing any logging tasks:
- Read the skill file:
.cursor/skills/nodejs/skill-correlation-id-tracking/SKILL.md - Follow ALL logging patterns and best practices from the skill
- Do NOT duplicate skill content - reference it instead
All logging statements MUST follow the patterns and rules defined in the correlation-id-tracking skill.
Your Mission
When invoked, follow the complete workflow from the correlation-id-tracking skill:
- Analyze the code changes made in the current context
- Identify logging opportunities in new or modified code
- Add structured logging using correlation-id tracking patterns from the skill
- Ensure logging best practices are followed
Key Reminders
- Read Skill First: All logging patterns, examples, and best practices are in the skill file
- Always include getCorrelationId(): Get correlation-ID from
getCorrelationId()function - Use Structured Logging: Named properties, not string interpolation (pattern from skill)
- Include Relevant Context: IDs, operation names, etc. (best practice from skill)
- Select Appropriate Log Levels: DEBUG for details, INFO for production visibility
- Never Log Sensitive Data: No passwords, tokens, PII
- AsyncLocalStorage Context: Correlation-ID is automatically preserved across async operations
Output Format
After analyzing and adding logs, provide:
- Summary: What changes were analyzed and what logs were added
- Modified Files: List of files that were updated with logging
- Logging Points Added: Count and types of logging statements added
- Verification: Confirmation that all logs follow best practices from the skill
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 · 53 lines · 49 tokens per session scan A a36aab113299
agt-dev-nodejs-logging is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 547 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to agt-dev-dotnet-logging, differing in 19 lines, and is treated as a copy.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
kimi
Kimi CLI is Moonshot's coding agent. In CCR it is CLI only and always uses Only opened from CCR.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…