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 jellydn/my-ai-toolsnpx agentmods add plugins/jellydn/my-ai-tools/codemapgit clone --depth 1 https://github.com/jellydn/my-ai-toolsWrote 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/jellydn/my-ai-tools/codemap)<a href="https://agentmods.dev/plugins/jellydn/my-ai-tools/codemap"><img src="https://agentmods.dev/badge/plugins/jellydn/my-ai-tools/codemap.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
codemap 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.
What it actually says
{
"name": "codemap",
"description": "Orchestrate parallel codebase analysis to produce 7 structured documents (STACK, INTEGRATIONS, ARCHITECTURE, STRUCTURE, CONVENTIONS, TESTING, CONCERNS) in .planning/codebase/.",
"version": "1.0.0",
"author": {
"name": "Dung Huynh Duc",
"email": "[email protected]"
},
"source": "./skills/codemap",
"category": "productivity",
"homepage": "https://github.com/jellydn/my-ai-tools"
}What ships with it
1 file beside marketplace.json#codemap 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.
- today First seen · 12 lines scan A 1e96ef7c6e37
codemap is a plugin published in the GitHub repository jellydn/my-ai-tools (119 stars, last pushed today), 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-09-03.
Other plugins, from other repositories
discover
Discover which AI agent to build — map automation outcomes to solvable opportunities, validate assumptions, and decide build vs buy. Use when exploring agent ideas, analyzing automation opportunities, running build-or-buy analysis, or estimating agent development costs.
auth
Auth skills for Claude Code — scaffold hand-rolled auth endpoints and audit auth code against security best practices.
devloop
Iterate until ready to merge: create branch, fix, commit, open PR, wait for AI review, apply feedback, repeat.
zenml-argo-migration
Migrate Argo Workflows to idiomatic ZenML pipelines with concept mapping, code translation, Kubernetes-native pattern flagging, and redesign guidance.
load-tester
Load and stress testing for APIs and web services.
migrate-tool
Generate database migrations and code migration scripts for framework upgrades.