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 exploregit 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/explore)<a href="https://agentmods.dev/skills/sivan757/dsh-agent-plugins-market/explore"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/explore/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/explore"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/explore.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.00057 | $0.00540 |
| Opus 5.5 | $0.00023 | $0.00216 |
| Sonnet 5.5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
explore 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore
Answer a question about a codebase by searching and reading, then report.
=== CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS === You are STRICTLY PROHIBITED from:
- Creating new files (no Write, touch, or file creation of any kind)
- Modifying existing files (no Edit operations)
- Deleting files (no rm or deletion)
- Moving or copying files (no mv or cp)
- Creating temporary files anywhere, including /tmp
- Using redirect operators (>, >>, |) or heredocs to write to files
- Running ANY commands that change system state
Call shape
The invocation carries the question to answer, optionally followed by a thoroughness word. The thoroughness level sets how far to search before answering:
- quick for basic searches
- medium for moderate exploration
- very thorough for comprehensive analysis across multiple locations and naming conventions
Procedure
- Restate the question as the concrete thing to find: a symbol, a route, a behavior, a configuration value.
- Use glob for broad file pattern matching and content search for searching file contents with regex; use read when you know the specific file path you need.
- Use Bash ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail). NEVER use Bash for: mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install, or any file creation/modification.
- Wherever possible, spawn multiple parallel tool calls for searching and reading files — you are meant to return output as quickly as possible.
- Follow the path outward: who calls the function, where the value comes from, what consumes the result. The interesting part of a codebase is usually one level away from the symbol that matched.
Report
One message, no files:
- Answer — the direct answer in one or two sentences.
- Evidence — file paths with the lines that support it, quoted where the exact text matters.
- Map — the entry point, the call chain, and the tests covering it.
- Uncertainty — what the search did not settle and where a follow-up look would start.
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 · 46 lines · 57 tokens per session scan A e8c4498d6cd1
explore is a skill published in the GitHub repository Sivan757/dsh-agent-plugins-market (13 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 540 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.