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/ogrodev/fsocietyWrote 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/ogrodev/fsociety/trenton)<a href="https://agentmods.dev/plugins/ogrodev/fsociety/trenton"><img src="https://agentmods.dev/badge/plugins/ogrodev/fsociety/trenton/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/ogrodev/fsociety/trenton"><img src="https://agentmods.dev/badge/plugins/ogrodev/fsociety/trenton.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trenton 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 2mo 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": "trenton",
"description": "Trenton — operational security plugin with Hexstrike MCP integration for Kali Linux. Machine hardening, VPS security, anti-forensics, and footprint elimination.",
"source": "./trenton/",
"author": {
"name": "Ogrodev"
}
}What it installs
The manifest is a name and a version. 5 skills, 12 commands, 2 agents travel with it, and installing the plugin installs all of them — 1,875 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill opsec-reporting A 274 tokens
- Skill network-anonymity A 247 tokens
- Skill vps-security A 266 tokens
- Skill anti-forensics B 271 tokens
- Skill system-hardening B 262 tokens
- Command op-vps A 19 tokens
- Command op-harden A 18 tokens
- Command op-clean A 12 tokens
- Command op-identity A 12 tokens
- Command op-proxy A 12 tokens
- Command op-campaign A 10 tokens
- Command op-planner A 14 tokens
- Command op-report A 18 tokens
- Command op-install A 14 tokens
- Command op-status A 18 tokens
- Command op-wipe C 14 tokens
- Command op-trace D 11 tokens
- Agent cleaner A 188 tokens
- Agent ghost A 195 tokens
What ships with it
1 file beside marketplace.json#trenton 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.
- 2mo ago First seen · 8 lines scan A d32a447444b2
trenton is a plugin published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo 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-09-03.
Other plugins, from other repositories
systems-architecture
Systems architecture and distributed systems skills including Designing Data-Intensive Applications (Martin Kleppmann), System Design Interview (Alex Xu), Clean Architecture (Robert C. Martin), Release It! (Michael Nygard), High Performance Browser Networking (Ilya Grigorik), and Team Topologies (Skelton & Pais).
cloudflare-nextjs
Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare). Use for SSR/ISR/SSG, App or Pages Router, getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars, or worker size/runtime/keepnames/FinalizationRegistry/connect.
cloudflare-queues
This skill should be used when the user asks to "set up Cloudflare Queues", "create a message queue", "implement queue consumer", "process background jobs", "configure queue retry logic", "publish messages to queue", "implement dead letter queue", or encountering "queue timeout", "message retry", "throughput exceeded".
cloudflare-browser-rendering
Cloudflare Browser Rendering with Puppeteer/Playwright. Use for screenshots, PDFs, web scraping, or encountering rendering errors, timeout issues, memory exceeded.
cloudflare-manager
Comprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing. Requires CLOUDFLAREAPIKEY in .env and Bun runtime with dependencies installed.
pulumi
Entry-point and specialized skills for writing and operating Pulumi infrastructure across CLI, projects, and Pulumi Cloud.