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 ItamarZand88/CLI-Anything-WEB --skill sync-checkgit clone --depth 1 https://github.com/ItamarZand88/CLI-Anything-WEBWrote 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/itamarzand88/cli-anything-web/sync-check)<a href="https://agentmods.dev/skills/itamarzand88/cli-anything-web/sync-check"><img src="https://agentmods.dev/badge/skills/itamarzand88/cli-anything-web/sync-check/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/itamarzand88/cli-anything-web/sync-check"><img src="https://agentmods.dev/badge/skills/itamarzand88/cli-anything-web/sync-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 161 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 162 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 163 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 164 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00095 | $0.01811 |
| Opus 5.5 | $0.00038 | $0.00724 |
| Sonnet 5.5 | $0.00019 | $0.00362 |
| Haiku 4.5 | $0.00010 | $0.00181 |
Grade A, and why
sync-check 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Check
After any code change, verify all related files are synchronized. This catches the "fixed the bug but forgot to update the skill/SOP/plugin docs" problem.
How to Use
Run /sync-check after making changes. It will:
- Detect what changed (from git diff or conversation context)
- Check all downstream files that depend on the change
- Report what's out of sync
- Offer to fix each one
The Dependency Web
Every change touches multiple files. Here's the full map:
Code Change → Documentation Updates
CLI code changed (client.py, commands/*.py, auth.py)
├── .claude/skills/<app>-cli/SKILL.md (commands, output fields, examples)
├── <app>/agent-harness/<APP>.md (SOP: rpcid table, data models)
├── <app>/agent-harness/cli_web/<app>/README.md (usage examples, deps)
├── <app>/agent-harness/setup.py (dependencies)
└── <app>_cli.py _print_repl_help() (REPL help must list all commands)
Bug Fix → Plugin Lesson Updates
Bug found and fixed in any CLI
├── Was it a pattern that could repeat in future CLIs?
│ YES → Add to the relevant plugin reference file:
│ ├── auth-strategies.md "Known Pitfalls" table (auth bugs)
│ ├── google-batchexecute.md (RPC/batchexecute bugs)
│ ├── ssr-patterns.md "HTML Scraping Pitfalls" (scraping bugs)
│ ├── protection-detection.md (anti-bot/WAF bugs)
│ └── traffic-patterns.md (protocol detection bugs)
│
├── Is it a universal lesson (applies to ALL CLIs)?
│ YES → Add to HARNESS.md "Lessons Learned" cross-reference table
│
└── Does it change a critical convention?
YES → Update CLAUDE.md "Critical Conventions" section
New Command Added → Full Update Chain
New command added to a CLI
├── .claude/skills/<app>-cli/SKILL.md (add command + options + output fields)
├── <app>_cli.py _print_repl_help() (add to REPL help)
├── <app>/agent-harness/<APP>.md (add endpoint to API map)
├── README.md (repo root) (if it changes the CLI's capabilities)
└── Run: cli-web-<app> <new-cmd> --json (verify output matches skill docs)
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 · 172 lines · 95 tokens per session scan A a6b4c113381b
sync-check is a skill published in the GitHub repository ItamarZand88/CLI-Anything-WEB (233 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 1,811 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-30.
Other skills, from other repositories
elnora-admin
This skill should be used when the user asks to "log in", "logout", "check auth", "create API key", "revoke API key", "list API keys", "check health", "submit feedback", "view audit log", "shell completions", "get account", "update account", "account details", "view agreements", "accept terms", "validate token"…
elnora-files
This skill should be used when the user asks to "list files", "read a file", "get file content", "view protocol output", "file versions", "version history", "download protocol", "upload file", "upload batch", "bulk upload", "create file", "archive file", "fork file", "promote file", "working copy", "commit working…
elnora-orgs
This skill should be used when the user asks to "list organizations", "create org", "org members", "billing", "invite member", "manage invitations", "list invitations", "resend invitation", "reinvite", "cancel invitation", "accept invitation", "get invitation info", "remove member from org", "organization library"…
elnora-platform
Use when the user asks about "Elnora platform", "elnora CLI", "platform API", "platform overview", "what commands are available", "elnora help", "how to use Elnora", or any general question about the Elnora AI Platform that doesn't fit a specific domain. Routes to domain-specific sub-skills for token-efficient…
elnora-tasks
This skill should be used when the user asks to "create a task", "send a message", "generate a protocol", "list tasks", "get task", "view task details", "read task messages", "update task status", "archive a task", "unarchive a task", "restore a task", "list archived tasks", "task attachments", "read an attachment"…
elnora-folders
This skill should be used when the user asks to "browse the knowledge base", "list KB folders", "show my folders", "open a folder", "create folder", "list folders", "rename folder", "move folder", "delete folder", "share a folder", "unshare a folder", "folder permissions", "who can access a folder", "organize files…