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 skills/hugorcd/evlog/create-map-rulenpx skills add HugoRCD/evlog --skill create-map-rulegit clone --depth 1 https://github.com/HugoRCD/evlogWhat 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.00074 | $0.02639 |
| Opus 5 | $0.00037 | $0.01319 |
| Sonnet 5 | $0.00015 | $0.00528 |
| Haiku 4.5 | $0.00007 | $0.00264 |
Grade A, and why
create-evlog-map-rule 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create an evlog map Rule (or Framework Adapter)
Extend the coverage scanner in @evlog/cli. Two kinds of extension:
- A rule: a new question asked of every entry point (
packages/cli/src/lib/map/rules/). This is the common case. - A framework adapter: teach
evlog mapto find entry points in a new framework (packages/cli/src/lib/map/adapters/). Rarer and heavier; see the last section.
PR Title
feat(cli): add the {id} map rule
The cli scope already exists, so no scope registration is needed.
Requirement or opportunity? Decide first
This is the design decision everything else follows from (see apps/docs/content/3.cli/3.rules.md for the published contract):
| Requirement | Opportunity | |
|---|---|---|
| Effect on the score | Costs weight points when it fails |
None, ever — the type forbids a weight |
| When it appears | Whenever it applies | Only when the project already uses the feature (appliesTo.when gated on project.features / project.pairable) |
| In the report | FIX FIRST / THEN |
GOING FURTHER |
Can fail a CI gate (--min-score, --baseline) |
Yes | No |
Guiding principle (from error-catalog.ts): a rule that fires on perfectly good code is policing, not helping. Opportunities must be gated on a signal that makes the case on its own (duplication, an installed package used without its evlog integration), never on "you could adopt a feature you don't use".
Current requirements: wide-event (40), audit (25), structured-errors (20), page-error-handling (20), context (15), error-handling (15). Current opportunities: error-catalog, audit-coverage, ai-logging, auth-identity.
Touchpoints Checklist (rule)
| # | File | Action |
|---|---|---|
| 1 | packages/cli/src/lib/map/rules/{id}.ts |
Create the rule (one exported const) |
| 2 | packages/cli/src/lib/map/rules/index.ts |
Import + one line in REGISTRY |
| 3 | packages/cli/src/lib/map/types.ts |
Add the id to the CheckId union (a type assert in index.ts fails the build if the registry and union drift) |
| 4 | packages/cli/test/map/rules.test.ts |
Add cases (the file has an ESLint-RuleTester-style Case harness — runRuleSet exercises one rule in isolation) |
| 5 | apps/docs/content/3.cli/3.rules.md |
Add a row to the Requirements or Opportunities table + a ### {title} section |
| 6 | apps/docs/content/3.cli/4.scoring.md |
Requirements only: reflect the new weight in the scoring explanation |
| 7 | skills/review-logging-patterns/references/code-review.md |
Add a row to the matching rules table |
| 8 | .changeset/{id}-map-rule.md |
Changeset for "@evlog/cli": minor |
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 · 159 lines · 74 tokens per session scan A 6eee3d6e2e4c
create-evlog-map-rule is a skill published in the GitHub repository HugoRCD/evlog (1,831 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 2,639 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 skills, from other repositories
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
golang-observability-opentelemetry
Instrumenting Go applications with OpenTelemetry for distributed tracing, Prometheus for metrics, and structured logging with slog.
Observability Checklist
Reviews a service or codebase against a full observability checklist — logs, metrics, traces, and alerting gaps.
anyrobot-shadcn-frontend-js
AnyRobot 前端开发核心指南：提供 JavaScript + React + shadcn/ui 开发的精简实用规范和最佳实践。 当用户需要前端开发指导、组件开发或项目结构建议时触发。 本技能提供实际可用于项目开发的核心代码示例和开发指南。.
数据模型文档生成
当用户要生成或更新 Doris 表的数据模型 Markdown（三一级标题：数据摘要、数据表列、JSON扩展字段）、从 Doris 拉取元数据与至少 100 行样本，并由脚本或 --llm 补全说明时启用。.
fix-loop
Use when a Java app that has stacktale installed is failing — after running it or its tests, to find what broke, fix it, and confirm the fix by re-running and checking for new errors. Also use when asked to "check the errors", "what's failing", or to work through errors-ai.log.