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 Sivan757/dsh-agent-plugins-market --skill initgit clone --depth 1 https://github.com/Sivan757/dsh-agent-plugins-marketWrote 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/sivan757/dsh-agent-plugins-market/init)<a href="https://agentmods.dev/skills/sivan757/dsh-agent-plugins-market/init"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/init/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/sivan757/dsh-agent-plugins-market/init"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/init.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.00048 | $0.03205 |
| Opus 5.5 | $0.00019 | $0.01282 |
| Sonnet 5.5 | $0.00010 | $0.00641 |
| Haiku 4.5 | $0.00005 | $0.00320 |
Grade A, and why
init 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 today.
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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up a minimal AGENTS.md (and optionally skills and hooks) for this repo. AGENTS.md is loaded into every session, so it must be concise — only include what the agent would get wrong without it.
Phase 1: Ask what to set up
When the invocation names --local, --skills or --hooks, preselect the matching choice below instead of asking that question; otherwise ask both questions.
Use ask_user_question to find out what the user wants:
-
"Which AGENTS.md files should /init set up?" Options: "Project AGENTS.md" | "Personal AGENTS.local.md" | "Both project + personal" Description for project: "Team-shared instructions checked into source control — architecture, coding standards, common workflows." Description for personal: "Your private preferences for this project (gitignored, not shared) — your role, sandbox URLs, preferred test data, workflow quirks."
-
"Also set up skills and hooks?" Options: "Skills + hooks" | "Skills only" | "Hooks only" | "Neither, just AGENTS.md" Description for skills: "On-demand capabilities you or the agent invoke with
/skill-name— good for repeatable workflows and reference knowledge." Description for hooks: "Deterministic shell commands that run on tool events (e.g., format after every edit). The agent can't skip them."
If an AGENTS.md already exists with content in this shape, read it first and ask whether to improve it in place as diffs or rewrite it.
Phase 2: Explore the codebase
Launch a subagent to survey the codebase, and ask it to read key files to understand the project: manifest files (package.json, Cargo.toml, pyproject.toml, go.mod, pom.xml, etc.), README, Makefile/build configs, CI config, existing AGENTS.md, assistant or editor rule files, .mcp.json.
Detect:
- Build, test, and lint commands (especially non-standard ones)
- Languages, frameworks, and package manager
- Project structure (monorepo with workspaces, multi-module, or single project)
- Code style rules that differ from language defaults
- Non-obvious gotchas, required env vars, or workflow quirks
- Existing
.agents/skills/directories and nested AGENTS.md files - Formatter configuration (prettier, biome, ruff, black, gofmt, rustfmt, or a unified format script like
npm run format/make fmt) - Git worktree usage: run
git worktree listto check if this repo has multiple worktrees (only relevant if the user wants a personal AGENTS.local.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.
- today First seen · 182 lines · 48 tokens per session scan A c6e3f0c3b838
init is a skill published in the GitHub repository Sivan757/dsh-agent-plugins-market (13 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 3,205 once invoked, about $0.0002 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-10-18.
Other skills, from other repositories
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
company-research-method
A documented process for researching a company using supplied files and selected public sources. It produces a company overview with business details, sourced financial figures, and stated risks.
promentor
A tool that turns a software project into a hands-on course in the style of an MIT course. It can produce lessons, code walkthroughs, practical labs, behavior tests, grading, explanations, and AI reviews.
dsh-plugin-guide
Use when developing, reviewing, packaging, debugging, or answering questions about DeepSeek Harness (DSH) plugins — the plugin-based agent harness on vendored Cordis. Applies the official plugin-development constraints (plugin contract, cordis.yml layers, services/events/effects, tool DSL, bundles/profiles) backed by…
delivery-proof
Delivery proof and the doublecheck report. Use when the work is done and the delivery must be proven — consolidate the spec, test timeline, review verdicts, and verification checks into a doublecheckreport, and only then claim completion.
playlet-wechat-feed
A daily report of popular short-drama articles from WeChat public accounts, a Chinese publishing platform, grouped by story themes and accompanied by writing insights.