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/andr-ca/agentharnessWrote 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/rules/andr-ca/agentharness/logging)<a href="https://agentmods.dev/rules/andr-ca/agentharness/logging"><img src="https://agentmods.dev/badge/rules/andr-ca/agentharness/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/rules/andr-ca/agentharness/logging"><img src="https://agentmods.dev/badge/rules/andr-ca/agentharness/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.00783 |
| Opus 5.5 | $0.00020 | $0.00313 |
| Sonnet 5.5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logging
This skill is self-contained for day-to-day use. Deeper reference (needs
the full harness checkout): patterns/logging/LOGGING_STANDARDS.md
(full mandate and config schema), patterns/logging/logging.yaml.example
(tested YAML template), patterns/logging/config_loader.py (Python
reference implementation with 99% test coverage).
When this applies
Full structured logging with YAML config, multiple backends, and
rotation is required at Production tier. Prototypes: print()/console.log()
is fine. Internal tools: structured logging recommended, single-backend
acceptable. Check the project's rigor tier first.
Log levels — pick the right one
| Level | Use for |
|---|---|
TRACE |
High-frequency per-call details; disabled in production by default |
DEBUG |
Developer diagnostic info; disabled in production by default |
INFO |
Normal operational events (startup, request completed) |
WARNING |
Something unexpected but recoverable; worth investigating |
ERROR |
A real failure that the system couldn't recover from |
CRITICAL |
The process must stop or data is corrupted |
Rule of thumb: if you'd page someone at 3am, it's ERROR or CRITICAL.
Structured logging: message + fields, never string interpolation
# WRONG: unstructured — can't query or filter by user_id or duration
logger.info(f"Request completed for user {user_id} in {duration}ms")
# RIGHT: message is a static label; context is in structured fields
logger.info("request.completed", user_id=user_id, duration_ms=duration)
// Node/pino/winston equivalent
logger.info({ userId, durationMs }, 'request.completed');
What NOT to log
Never log: passwords, tokens, API keys, full credit card numbers, SSNs, session IDs, or any data under a PII/GDPR policy. Redact or omit before logging. If logging usefulness and secrecy conflict, redact. Do not log the secret "for completeness."
# WRONG: logs the raw token
logger.info("auth.token_issued", token=issued_token)
# RIGHT: log only what's safe to expose
logger.info("auth.token_issued", user_id=user_id, expires_at=exp)
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 · 93 lines · 49 tokens per session scan A 5d45c5c29465
logging is a cursor rule published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 783 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other cursor rules, from other repositories
root-cause-first
Require source-level fixes for malformed or polluted domain data.
debugging
Debugging discipline. Apply when investigating a bug, test failure, or unexpected behavior.
crew
Crew Mate production-change checklist for one failing target.
windsurfrules
This repo has a GraphPilot structural code-graph available via MCP. Use it before grep on structural questions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.