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 zjp1997720/zhijian-skills --skill skill-open-sourcergit clone --depth 1 https://github.com/zjp1997720/zhijian-skillsWrote 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/zjp1997720/zhijian-skills/skill-open-sourcer)<a href="https://agentmods.dev/skills/zjp1997720/zhijian-skills/skill-open-sourcer"><img src="https://agentmods.dev/badge/skills/zjp1997720/zhijian-skills/skill-open-sourcer/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/zjp1997720/zhijian-skills/skill-open-sourcer"><img src="https://agentmods.dev/badge/skills/zjp1997720/zhijian-skills/skill-open-sourcer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 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 MCP Rug Pull · line 3 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 68 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 75 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 93 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 139 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00103 | $0.02434 |
| Opus 5 | $0.00051 | $0.01217 |
| Sonnet 5 | $0.00021 | $0.00487 |
| Haiku 4.5 | $0.00010 | $0.00243 |
Grade A, and why
skill-open-sourcer 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 7d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Open Sourcer
Publish every public Skill from the single canonical repository: https://github.com/zjp1997720/zhijian-skills.
Hard publishing boundary
- A
SKILL.mdpath or Skill directory is an import candidate, not a request to create a repository. - Put the complete agent payload in
skills/<name>/, human docs indocs/skills/<name>/, and release notes indocs/changelogs/<name>.md. - Register the Skill in
registry/skills.json. Never addmirror,mirror_tag, standalone repository, redirect workflow, or mirror-export metadata. - Publish commits, per-Skill Tags, and install instructions only from
zjp1997720/zhijian-skills. - Stop on secrets, private paths, client data, unpublished proprietary material, unclear asset ownership, or an unverified canonical remote.
Read Portfolio mode, Registry contract, Release package, and README design before writing.
Workflow
- Resolve the input to a real Skill directory. Accept a
SKILL.md, its containing directory, or a symlink from a local Skill root. - Resolve the canonical checkout from the current repository,
ZHIJIAN_SKILLS_REPO, or~/Documents/GitHub/zhijian-skills. Verifyoriginresolves tozjp1997720/zhijian-skills; never guess another destination. - Follow the canonical repository's Git synchronization rules. Run
git_sync_guard.py check --repo <zhijian-skills>before changing or publishing from an existing checkout; aneeds-syncmarker is a hard stop. Then run:
SKILL_OPEN_SOURCER_DIR="<zhijian-skills>/skills/skill-open-sourcer"
python3 "$SKILL_OPEN_SOURCER_DIR/scripts/check_release_env.py" \
--repo-dir <zhijian-skills> --check-npx-skills
python3 "$SKILL_OPEN_SOURCER_DIR/scripts/scan_skill_release.py" \
/path/to/skill-or-SKILL.md
- Inspect
SKILL.mdand directly referencedagents/,references/,scripts/, andassets/. Copy only the complete, sanitized install payload intoskills/<name>/; preserve required license and third-party notices. - Write the eight-field release story from README design, choose
clean-docorproof-led, then create or update bilingual docs, Changelog, Registry record, Portfolio catalog, and project-native visuals. A proof-led Hero must use a composition derived from the Skill's real mechanism or output; changing only the title and motif inside a shared layout fails review. Never expose a root-levelSKILL.mdor add human README files inside the Skill payload. - Choose the version with version-contract.md. Use only the canonical Tag
<skill>/v<version>. - Freeze a release plan with the narrowest selector. For a governed Skill, its
manifest.jsonmust declaretrust_reportandoutput_quality_scorecardas files inside the install payload; both files must exist and be tracked atHEAD. Planning fails before candidate refs are created when either baseline is undeclared, missing, untracked, or escapes the payload. Use--skill <name>for one Skill; reserve--alland optional--excludefor an intentional multi-Skill wave:
What ships with it
23 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 236 B
- LICENSE 1.0 KB
- references/portfolio-mode.md 1.6 KB
- references/readme-design.md 8.8 KB
- references/registry-contract.md 868 B
- references/release-contract.md 2.2 KB
- references/release-package.md 4.6 KB
- references/security-contract.md 905 B
- references/third-party-notices.md 1.4 KB
- references/version-contract.md 726 B
- scripts/audit_release_readme.py 13 KB runs code
- scripts/check_release_env.py 6.1 KB runs code
- scripts/git_sync_guard.py 7.1 KB runs code
- scripts/manage_local_links.py 11 KB runs code
- scripts/portfolio.py 14 KB runs code
- scripts/release_portfolio.py 23 KB runs code
- scripts/scan_skill_release.py 10 KB runs code
- scripts/verify_isolated_install.py 7.6 KB runs code
- tests/test_audit_release_readme.py 7.7 KB runs code
- tests/test_release_selection.py 11 KB runs code
- tests/test_scan_skill_release.py 4.0 KB runs code
- tests/test_skill_contract.py 3.0 KB runs code
- tests/test_verify_isolated_install.py 5.9 KB runs code
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.
- 7d ago Changed · +1 lines 1b5fc4400e8b
- 13d ago First seen · 143 lines · 103 tokens per session scan A dec46958d8a5
skill-open-sourcer is a skill published in the GitHub repository zjp1997720/zhijian-skills (680 stars, last pushed 7d ago), licensed MIT. It adds 103 tokens to every session and 2,434 once invoked, about $0.0005 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…