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.
/plugin marketplace add JHostalek/dotclaudenpx agentmods add plugins/jhostalek/dotclaude/dotclaudegit clone --depth 1 https://github.com/JHostalek/dotclaudeGrade A, and why
jhostalek-skills 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 2d 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
{
"name": "jhostalek-skills",
"version": "1.4.0",
"description": "JHostalek's opinionated agent skills for planning, auditing, shipping, and improving software.",
"author": {
"name": "Jan Hostalek",
"url": "https://github.com/JHostalek"
},
"homepage": "https://github.com/JHostalek/dotclaude",
"repository": "https://github.com/JHostalek/dotclaude",
"license": "CC0-1.0",
"keywords": [
"engineering",
"skills",
"audit",
"git",
"design"
],
"skills": [
"./skills/audit-comments",
"./skills/audit-complexity",
"./skills/audit-contracts",
"./skills/audit-correctness",
"./skills/audit-data-integrity",
"./skills/audit-error-handling",
"./skills/audit-logs",
"./skills/audit-necessity",
"./skills/audit-patterns",
"./skills/audit-perf",
"./skills/audit-reliability",
"./skills/audit-security",
"./skills/audit-structure",
"./skills/audit-tests",
"./skills/audit",
"./skills/commit",
"./skills/design-refiner",
"./skills/design",
"./skills/judge",
"./skills/merge",
"./skills/plan",
"./skills/pr",
"./skills/prompt",
"./skills/rebase",
"./skills/sparring",
"./skills/sota",
"./skills/timesheet",
"./skills/transformer",
"./skills/ux",
"./skills/writing-identity",
"./skills/yeet"
]
}
What ships with it
1 file beside plugin.json 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.
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.
- 2d ago First seen · 53 lines scan A 2cfa7b3c9947
jhostalek-skills is a plugin published in the GitHub repository JHostalek/dotclaude (10 stars, last pushed 27d ago), licensed CC0-1.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
tlive
Plugin marketplace listing 1 plugin: tlive.
tlive
tlive hooks + skill + commands — IM approvals, session monitoring, web terminal.
director-mode-lite
Guidance-first workflows shared by Claude Code, Codex CLI, and Grok Build.
director-mode-lite
Guidance-first Director workflows for Claude Code, Codex CLI, and Grok Build, with portable session relay and native adapters.
backend-architecture
Small, opinionated architecture guide for production backend services across languages and frameworks.
backend-validator
Backend API and WebSocket validation via Hurl, websocat, and oauth2c with OIDC token caching.