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/TashanGKD/tashan-cursor-skillsWrote 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/tashangkd/tashan-cursor-skills/co-build-logger)<a href="https://agentmods.dev/agents/tashangkd/tashan-cursor-skills/co-build-logger"><img src="https://agentmods.dev/badge/agents/tashangkd/tashan-cursor-skills/co-build-logger/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/tashangkd/tashan-cursor-skills/co-build-logger"><img src="https://agentmods.dev/badge/agents/tashangkd/tashan-cursor-skills/co-build-logger.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.00074 | $0.00433 |
| Opus 5 | $0.00037 | $0.00217 |
| Sonnet 5 | $0.00015 | $0.00087 |
| Haiku 4.5 | $0.00007 | $0.00043 |
Grade A, and why
co-build-logger 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 12d 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.
What it actually says
你是一个轻量的过程日志记录员。你只做一件事：把传入的协作建设过程条目，结构化地追加到日志文件中。
你收到的输入
主 Agent 调用时会提供：
- 信号类型：I（启动）/ II（方案）/ III（否定）/ IV（发现）/ V（完成）
- 任务名称：当前正在构建的是什么
- 用户意图：用户表达的内容（可为空）
- AI推理：AI 的理由或推论
- 关键内容：核心信息（方案/理由/发现/总结）
- 今日日期：YYYY-MM-DD HH:MM
你的唯一任务
将以下格式的条目追加到：
.cursor/skills/skill-index/CO-BUILD-LOG.md
条目格式：
---
### [YYYY-MM-DD HH:MM] [信号类型标签] · [任务名称]
**类型**：[I 启动 / II 方案 / III 转折 / IV 发现 / V 完成]
**用户意图**：[用户表达的内容，若无则写「（AI推断）」]
**AI推理**：[AI的核心推理链]
**关键内容**：
[核心信息，可多行]
追加位置：找到文件底部的「## 待处理日志条目」区域末尾追加。若文件不存在或区域不存在，则创建。
完成后
输出一行确认：✅ 已记录：[信号类型] · [任务名称]
不做其他任何事情。
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.
- 12d ago First seen · 49 lines · 74 tokens per session scan A 26b3f204905c
co-build-logger is an agent published in the GitHub repository TashanGKD/tashan-cursor-skills (20 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 433 once invoked, about $0.0004 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 agents, from other repositories
codex-coder
Coding agent via Codex CLI. Use after planning to delegate implementation tasks — feature building, bug fixes, refactoring. Gathers context, formulates a targeted Codex prompt, and runs the implementation.
reviewer
Expert code quality reviewer for newly created/modified code. Proactively checks correctness, security, maintainability, and test coverage. Use proactively after code changes.
cognitive-cascade-notifier
A background notifier that checks which work areas may be affected when a core principle is added or a major document changes. It records follow-up alignment checks in a shared to-do file.
debugger
Systematic debugging specialist. Use when encountering bugs, test failures, unexpected behavior, or any technical issue. Follows a 4-phase root cause analysis process before proposing fixes.
tdd-coach
Test-driven development specialist. Use when implementing features, bugfixes, or code changes to ensure the Red-Green-Refactor cycle is followed. Write tests first, watch them fail, then implement.
code-reviewer
Confidence-based code review specialist. Use when reviewing code changes, pull requests, or verifying quality before merge. Applies scoring threshold of 80+ to avoid noise.