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/LandonSchropp/agent-toolkitWrote 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/landonschropp/agent-toolkit/ls-browser)<a href="https://agentmods.dev/plugins/landonschropp/agent-toolkit/ls-browser"><img src="https://agentmods.dev/badge/plugins/landonschropp/agent-toolkit/ls-browser/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/landonschropp/agent-toolkit/ls-browser"><img src="https://agentmods.dev/badge/plugins/landonschropp/agent-toolkit/ls-browser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ls-browser 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": "ls-browser",
"description": "Browser automation skills",
"version": "0.0.0",
"author": {
"name": "Landon Schropp"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 45 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 9 lines scan A 1895099b0501
ls-browser is a plugin published in the GitHub repository LandonSchropp/agent-toolkit (3 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-08-31.
Other plugins, from other repositories
capacitor-core
Core Capacitor skills for best practices, plugin selection, and MCP automation.
contentful
Agent skills for Contentful apps, APIs, migrations, and personalization.
contentful
Contentful apps, API, migration, and personalization skills.
firecrawl
Web scraping, search, crawling, and file parsing through the firecrawl-cli binary with a write-to-disk-then-Read pattern that keeps large results out of context: a user-facing wrapper skill, a lazy-install setup skill, and a separate gated maintainer update skill tracking the upstream CLI and skill source.
typefox-agent-skills
General-purpose agent skills from TypeFox. They capture engineering practices, development workflows, and writing guidance that apply across codebases.
transformation
Digital maturity assessment, Now/Next/Later transformation roadmaps, target operating model design, technology strategy briefs, and transformation business cases.