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.
git clone --depth 1 https://github.com/gnoyes-mik/code-tourWrote 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/plugins/gnoyes-mik/code-tour/marketplace)<a href="https://agentmods.dev/plugins/gnoyes-mik/code-tour/marketplace"><img src="https://agentmods.dev/badge/plugins/gnoyes-mik/code-tour/marketplace/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/plugins/gnoyes-mik/code-tour/marketplace"><img src="https://agentmods.dev/badge/plugins/gnoyes-mik/code-tour/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-tour-marketplace 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 1mo 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": "code-tour-marketplace",
"owner": {
"name": "gnoyes-mik"
},
"plugins": [
{
"name": "code-tour",
"source": {
"source": "github",
"repo": "gnoyes-mik/code-tour"
},
"description": "Interactive code explorer - navigate your codebase like a debugger",
"version": "1.0.0"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.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.
- 1mo ago First seen · 18 lines scan A 73f9206af51b
code-tour-marketplace is a plugin published in the GitHub repository gnoyes-mik/code-tour (3 stars, last pushed 9mo ago), licensed MIT. 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
log-correlation
Correlates and troubleshoots logs across OS, AWS, application, and web server sources. Extensible via log-types/ definitions.
rust-intel
Defense against LLM Rust failure modes: 59 categories of bugs that survive rustc, clippy, and cargo test — async cancellation, unsafe/FFI, concurrency, crypto, supply-chain, tests-that-pass-by-luck, semantic conformance, and systemic performance cost. Ships the rust-intel skill plus /rust-intel:audit, /rust-intel:fix.
dive-deeper
Deep-dive analysis skill for planning phase — trace execution paths, find related code, surface edge cases and potential problems.
duda
DUDA — Isolation Guardian. Prevents, diagnoses, and recovers isolation contamination in multi-layered architectures.
api-authentication
Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors.
csrf-protection
Implements CSRF protection using synchronizer tokens, double-submit cookies, and SameSite attributes. Use when securing web forms, protecting state-changing endpoints, or implementing defense-in-depth authentication.