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 skills add XyrusCode/ai-sync --skill de-claudegit clone --depth 1 https://github.com/XyrusCode/ai-syncWrote 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/xyruscode/ai-sync/de-claude)<a href="https://agentmods.dev/skills/xyruscode/ai-sync/de-claude"><img src="https://agentmods.dev/badge/skills/xyruscode/ai-sync/de-claude/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/xyruscode/ai-sync/de-claude"><img src="https://agentmods.dev/badge/skills/xyruscode/ai-sync/de-claude.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.00111 | $0.04835 |
| Opus 5.5 | $0.00044 | $0.01934 |
| Sonnet 5.5 | $0.00022 | $0.00967 |
| Haiku 4.5 | $0.00011 | $0.00483 |
Grade A, and why
de-claude 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
de-claude: remove AI fingerprints from a repository
humanizer fixes prose. This fixes everything a repo leaks besides prose: trailers, authorship, history, branch names, config files, and comments that narrate a diff. When a commit message body needs prose work, use humanizer on the body and come back here for the mechanics.
The single most important rule: rewriting history is destructive and cannot be undone once you have deleted the backups. Read "Scope before you touch" first, every time. A repo that is merely embarrassing is recoverable. A repo whose shared history you rewrote without asking is a Monday morning outage for everyone else who cloned it.
What actually leaks
Ordered by how reliably it identifies a tool. The top group is a fingerprint. The bottom group is a guess.
Tier 1: unambiguous
- Commit trailers.
Co-Authored-By: Claude <[email protected]>,Co-Authored-By: Claude Opus 4.8 <[email protected]>,Co-authored-by: Cursor Agent,Co-authored-by: Copilot,Co-authored-by: openai-codex[bot]. - Generated-with footers in commits, PR bodies, and issue bodies:
🤖 Generated with [Claude Code](https://claude.com/claude-code),Generated with Cursor,Created by Devin. - Bot authorship. Check author and committer separately.
[email protected],[email protected],*[bot]@users.noreply.github.com,devin-ai-integration[bot]. - Branch names:
claude/*,cursor/*,codex/*,devin/*,copilot/*. - Assistant config committed by accident:
.claude/,CLAUDE.md,.cursor/,.cursorrules,.aider*,.github/copilot-instructions.md,.windsurfrules,AGENTS.md,.specstory/. - Attribution in docs: "Built with Claude Code", "This project was generated by...".
Tier 2: strong but circumstantial
- Em dashes in commit subjects. Almost nobody reaches for
—in a terminal. - Commit bodies with bolded inline headers, or
**Changes:**followed by a bulleted rule of three. - Subjects in Title Case, or subjects over ~72 chars that read like documentation.
- Emoji-prefixed subjects in a repo that has no gitmoji convention.
- A body that explains the why of something trivial at three-paragraph length.
- Suspiciously uniform commit cadence: forty commits in one hour, every message the same shape.
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 · 274 lines · 111 tokens per session scan A 7f6ba8f3d377
de-claude is a skill published in the GitHub repository XyrusCode/ai-sync (2 stars, last pushed 18d ago), licensed MIT. It adds 111 tokens to every session and 4,835 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…