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/whitebeardit/.cursorWrote 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/whitebeardit/.cursor/agt-dev-nodejs-logging)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-dev-nodejs-logging"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-nodejs-logging/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/whitebeardit/.cursor/agt-dev-nodejs-logging"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-nodejs-logging.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.00547 |
| Opus 5.5 | $0.00020 | $0.00219 |
| Sonnet 5.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 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.
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.
- 1mo 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 7mo ago), licensed MIT. It adds 49 tokens to every session and 547 once invoked, about $0.0002 per session on Opus 5.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
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
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.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.