agentmods.dev

hesoyam-for-claude-code: Skill for Claude Code

.claude/skills/ecosystem-check/SKILL.md

ecosystem-check is a skill for Claude Code from Shashank2577/hesoyam-for-claude-code. It costs 15 tokens per session (417 once invoked), scanned A, original, MIT.

A scheduled review process for checking versions, updates, and new additions in the Claude Code ecosystem and related tools. It also evaluates possible new tools against maintenance, documentation, cost, and compatibility questions.

In plain words
What is it for?
Use it for monthly dependency checks, catalogue scans, changelog reviews, breaking-change checks, and quick evaluations of newly discovered tools.
Why use it?
It reduces the need to manually track changes across several dependencies and tool catalogues. It puts update details and possible risks into one report.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents; mentions Claude Code.

This is Shashank2577/hesoyam-for-claude-code's own configuration. It tells Claude Code how to work on hesoyam-for-claude-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hesoyam-for-claude-code configures →

not rated 11repo 7mo ago A scan 15 tokens original MIT
View source ↗ Shashank2577/hesoyam-for-claude-code
Reuse

Borrowing it

Nothing to install: this file belongs to Shashank2577/hesoyam-for-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Shashank2577/hesoyam-for-claude-code/main/.claude/skills/ecosystem-check/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Shashank2577/hesoyam-for-claude-code

Made for: Claude Code.

Wrote 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.

agentmods badge for ecosystem-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/shashank2577/hesoyam-for-claude-code/ecosystem-check/github.svg)](https://agentmods.dev/skills/shashank2577/hesoyam-for-claude-code/ecosystem-check)
Your own site
<a href="https://agentmods.dev/skills/shashank2577/hesoyam-for-claude-code/ecosystem-check"><img src="https://agentmods.dev/badge/skills/shashank2577/hesoyam-for-claude-code/ecosystem-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.

agentmods 80×15 button for ecosystem-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/shashank2577/hesoyam-for-claude-code/ecosystem-check"><img src="https://agentmods.dev/badge/skills/shashank2577/hesoyam-for-claude-code/ecosystem-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 417 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00417
Opus 5.5 $0.00006 $0.00167
Sonnet 5.5 $0.00003 $0.00083
Haiku 4.5 $0.00002 $0.00042

Measured 2mo ago against content hash 17c6bed507c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ecosystem-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 2mo 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.

.claude/skills/ecosystem-check/SKILL.md · 58 lines

What it actually says

$VAULT_PATH defaults to ~/Documents/obsidian-vault. Override by setting VAULT_PATH in your environment or passing --vault-path during install.

Run a monthly ecosystem check across the HESOYAM dependency stack.

Step 1: Check upstream versions.

For each core dependency, check the latest release:

  • oh-my-claudecode (npm: oh-my-claude-sisyphus)
  • everything-claude-code
  • claude-mem
  • obsidian-skills
  • claudesidian
  • notebooklm-py

Report: current version vs latest, changelog highlights, breaking changes.

Step 2: Scan ecosystem catalogs.

Check these catalogs for new additions relevant to the user's stack:

  • awesome-claude-code — new skills, agents, MCPs
  • awesome-claude-code-subagents — new specialized subagents
  • awesome-claude-skills — new cross-platform skills

Step 3: Evaluate new finds.

For each promising new tool, quick-evaluate:

Question Answer
Does it solve a real problem?
Actively maintained? (commit < 30 days)
Has documentation?
Token cost estimate?
Conflicts with existing tools?

Step 4: Report.

## Ecosystem Check — [date]

### Version Updates
| Tool | Installed | Latest | Action |
|------|-----------|--------|--------|
| ... | ... | ... | Update / Skip / Breaking |

### New Discoveries
- [Tool name] — [one-line description] — [recommended / skip / evaluate later]

### Recommended Actions
1. [Specific action items]

Save the report to Obsidian vault if configured ($VAULT_PATH/03_Resources/ecosystem/[date].md).

Changes

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.

  1. 2mo ago First seen · 58 lines · 15 tokens per session scan A 17c6bed507c8

Subscribe to this mod's changes

ecosystem-check is a skill published in the GitHub repository Shashank2577/hesoyam-for-claude-code (11 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 417 once invoked, about $0.0001 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.

Building agents
Related

ecosystem-check compared with skills from other repositories

ecosystem-check next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ecosystem-checkShashank2577/hesoyam-for-claude-codeSkill117mo agoMITA15Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code