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 agentmods add skills/bartholomej/node-csfd-api/validate_changesnpx skills add bartholomej/node-csfd-api --skill validate_changesgit clone --depth 1 https://github.com/bartholomej/node-csfd-apiWhat 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 | $0.00025 | $0.00319 |
| Opus 5 | $0.00013 | $0.00160 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
Validate Changes 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 yesterday.
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
Validate Changes
Since this project relies on scraping a 3rd party website (CSFD.cz), validation is crucial to ensure their DOM hasn't changed or our logic isn't broken.
1. Static Analysis & Build
Ensure that TypeScript compiles and the dual-build system works.
# Checks types and builds both 'server' and 'mcp-server' related outputs
yarn build
2. Unit & Integration Tests
Run the test suite. Note that some tests might hit the real CSFD website.
yarn test
3. Real-world Demo
The demo.ts file is a scratchpad for testing the actual scraper against current CSFD pages.
# Run the demo script
npm run demo
If the demo fails:
- Check your internet connection (CSFD might block generic IPs).
- Check if CSFD changed their DOM layout.
- Verify
User-Agentheaders insrc/fetchers/fetcher.ts.
4. MCP Server Check
If you modified mcp-server/, verify it builds and starts.
# Build specific to MCP
yarn build:mcp
# Try to run it (it handles stdio, so it will just wait for input, but shouldn't crash immediately)
node dist/bin/mcp-server.js
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.
- yesterday First seen · 53 lines · 25 tokens per session scan A 521fb0f0611a
Validate Changes is a skill published in the GitHub repository bartholomej/node-csfd-api (60 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 319 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-30.
Other skills, from other repositories
git-cleanup
Clean up local git branches and remotes accumulated from PR reviews. Use when the user asks to clean branches, remove stale remotes, or tidy up the local git state.
submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.
pre-impl-discussion
Conduct a thorough pre-implementation discussion before making significant changes. Use when the user wants to discuss, plan, or evaluate a change before implementing it — especially when they say words like 'discuss', 'evaluate', 'plan', or 'let's talk about'.
livecodes/framework-wrappers
Use SDK with React, Vue, Svelte, Solid, Preact, and Web Components. sdkReady callback pattern, reactive props, and framework-specific setup. Load this skill when embedding LiveCodes in a framework application.
livecodes
Open-source, client-side code playground supporting 90+ languages/frameworks. Runs entirely in the browser with SDK for embedding. Entry point for all LiveCodes skills.
livecodes/sdk-methods
Use SDK methods to interact with playgrounds: run, getCode, setConfig, getConfig, watch, runTests, format, getShareUrl, show, destroy. Load this skill when programmatically controlling embedded playgrounds, reacting to code changes, or retrieving compiled output.