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/contributingnpx skills add HugoRCD/evlog --skill contributinggit 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.00068 | $0.01692 |
| Opus 5 | $0.00034 | $0.00846 |
| Sonnet 5 | $0.00014 | $0.00338 |
| Haiku 4.5 | $0.00007 | $0.00169 |
Grade A, and why
contributing 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributing to evlog
The repository's own AGENTS.md is the source of truth for all of this. It changes; this skill does not restate it in full on purpose. Read AGENTS.md from the repo before giving specifics.
Your system context has a Workspace section saying whether the repository is checked out on this turn. With a checkout, read_file /workspace/AGENTS.md: free, and at the ref you were summoned on. Without one, github__getFileContent on AGENTS.md at the root of HugoRCD/evlog.
What follows is the shape of the answer, so you know what to look for and what to warn about.
The parts people get wrong
- A changeset is required for anything a consumer of evlog would notice: a feature, a bug fix, a breaking change.
pnpm changeset, committed alongside the code. Changes confined toapps/*orexamples/*never need one. A PR without a changeset for a user-facing change does not merge. - Conventional Commits, lowercase subject.
feat: add stream server, notfeat: Add stream server. Omit the scope when the change is cross-cutting; never useevlogas a scope. A new subsystem needs its scope registered in both.github/workflows/semantic-pull-request.ymland.github/pull_request_template.md, and because title validation reads the base branch, that registration has to land in an earlier PR. - The scope list is a closed set, and you read it before you write the title.
.github/workflows/semantic-pull-request.ymlholds the only scopes CI accepts. Anything else failsValidate PR title, and a scope that merely sounds plausible (evlog, the package name, the app directory) is the usual way that happens. A change confined toapps/docsisdocs:, with no scope:docsis already the type. - A bug fix needs a failing regression test first, then the fix.
- New exports go in
packages/evlog/package.json(exportsandtypesVersions) andtsdown.config.ts. - Skills must stay in sync. If a change touches something a skill documents, the SKILL.md changes in the same PR, both the internal
.agents/skills/and the publishedskills/.
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 · 76 lines · 68 tokens per session scan A 5cf94b5e9009
contributing is a skill published in the GitHub repository HugoRCD/evlog (1,831 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,692 once invoked, about $0.0003 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…
commit
Use when 使用者要求把工作區的變更寫進版本歷史，不論用詞是 commit、提交、送進 git 還是「整理一下」；需要拆成多筆時同樣適用。NOT for 把 clade 改動散播到 consumer（走 /clade-publish），NOT for 建 / 合併 worktree（走 /wt）。.
golang-observability-opentelemetry
Instrumenting Go applications with OpenTelemetry for distributed tracing, Prometheus for metrics, and structured logging with slog.
rsyslog_commit
Ensures compliance with rsyslog's strict commit message and branching policies.
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 开发的精简实用规范和最佳实践。 当用户需要前端开发指导、组件开发或项目结构建议时触发。 本技能提供实际可用于项目开发的核心代码示例和开发指南。.