Borrowing it
Nothing to install: this file belongs to Luckycat133/traecnclaw-mcp-skill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Luckycat133/traecnclaw-mcp-skill/main/.agents/skills/traecnclaw-mirror-maintenance/SKILL.mdgit clone --depth 1 https://github.com/Luckycat133/traecnclaw-mcp-skillWrote 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/skills/luckycat133/traecnclaw-mcp-skill/traecnclaw-mirror-maintenance)<a href="https://agentmods.dev/skills/luckycat133/traecnclaw-mcp-skill/traecnclaw-mirror-maintenance"><img src="https://agentmods.dev/badge/skills/luckycat133/traecnclaw-mcp-skill/traecnclaw-mirror-maintenance/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/skills/luckycat133/traecnclaw-mcp-skill/traecnclaw-mirror-maintenance"><img src="https://agentmods.dev/badge/skills/luckycat133/traecnclaw-mcp-skill/traecnclaw-mirror-maintenance.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.00046 | $0.00529 |
| Opus 5.5 | $0.00018 | $0.00212 |
| Sonnet 5.5 | $0.00009 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
traecnclaw-mirror-maintenance 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 — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TRAECNclaw mirror maintenance
Read SOURCE_REVISION, release-manifest.json, README.md and the affected workflow. This repository is a public distribution mirror; it is not the canonical gateway implementation.
Choose the owner
.codex/skills/traecnclaw-mcp/is generated from the canonical repository'sskills/traecnclaw-mcp/. Correct runtime Skill content upstream, then review the complete pinned, allowlisted release export; hand edits here can be overwritten by later generation.- The legacy
.github/workflows/sync-canonical.ymlis disabled: it has no token permissions or checkout and rejects every legacy dispatch. It does not copy the Skill subtree, updateSOURCE_REVISIONor push publicly. Do not restore it; a future publisher must review fixed provenance and the complete export before public writes. - Maintainer-only guidance under
.agents/must not be inserted into the portable public operator Skill or its release archive.
For drift, compare the recorded canonical revision, intended source revision, mirrored Skill version, manifest artifact/version fields and README install commands separately. Do not overwrite unrelated local changes or infer that a successful sync PR published a release. Canonical access may be unavailable; report the unresolved source comparison instead of fabricating provenance.
Verify the relevant claim
The current mirror validation workflow uses node scripts/verify-public-distribution.js --checkout to inventory distribution and exact maintenance paths separately, without following maintenance links. It passes only the 35-file distribution snapshot to the strict pinned-byte guard; the canonical exporter retains its separate 22-output contract. Unknown checkout paths and generated archives are rejected. Run the accompanying offline test file as well. These checks do not establish MCP behavior or a working published install. For Skill-contract changes, use the portable tests under .codex/skills/traecnclaw-mcp/scripts/ after inspecting their launcher requirements. For a release/install claim, verify the exact artifact, its checksum, the installed server version and stdio discovery on the intended host.
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 Changed 0cf3e2b37161
- 20d ago First seen · 23 lines · 46 tokens per session scan A 801b26a40854
traecnclaw-mirror-maintenance is a skill published in the GitHub repository Luckycat133/traecnclaw-mcp-skill (0 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 529 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-10-07.
Other skills, from other repositories
plugin-publish
A release guide for publishing Zhin.js plugins to npm, the JavaScript package registry, and to the Zhin plugin marketplace. It covers package metadata, versioning, release checks, and submission requirements.
launch-and-growth
Get an open-source project in front of the people who need it, and keep them. Use when preparing to announce a project, writing a Hacker News or Reddit or Product Hunt post, planning a launch, writing a blog post about a release, improving GitHub discoverability (topics, About, social preview), or when the user asks…
release-engineering
Version, changelog, tag, and publish a release. Use when cutting a release, setting up automated publishing to npm/PyPI/crates.io/Maven/Homebrew, deciding whether a change is major/minor/patch, writing release notes, adopting conventional commits or changesets, planning a 1.0, or handling a bad release that needs to…
clawhub-production-release
Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.
release-announcement
A release-promotion tool that turns a project's latest Markdown release notes into a short WeChat group message and a vertical PNG poster. It checks GitHub contributor IDs and downloads their real public profile pictures; it does not create or publish a GitHub Release.
omh-release-cut
This is an OMH release-cut workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).