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.
curl -O https://raw.githubusercontent.com/Shashank2577/hesoyam-for-claude-code/main/.claude/skills/ecosystem-check/SKILL.mdgit clone --depth 1 https://github.com/Shashank2577/hesoyam-for-claude-codeWrote 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/shashank2577/hesoyam-for-claude-code/ecosystem-check)<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.
<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>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.00015 | $0.00417 |
| Opus 5 | $0.00008 | $0.00209 |
| Sonnet 5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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 11d 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.
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).
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.
- 11d ago First seen · 58 lines · 15 tokens per session scan A 17c6bed507c8
ecosystem-check is a skill published in the GitHub repository Shashank2577/hesoyam-for-claude-code (11 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 417 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…