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 agentmods add agents/thomascasali/claude-kb-workflow/securitygit clone --depth 1 https://github.com/thomascasali/claude-kb-workflowWrote 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/agents/thomascasali/claude-kb-workflow/security)<a href="https://agentmods.dev/agents/thomascasali/claude-kb-workflow/security"><img src="https://agentmods.dev/badge/agents/thomascasali/claude-kb-workflow/security.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.02271 |
| Opus 5 | $0.00019 | $0.01136 |
| Sonnet 5 | $0.00008 | $0.00454 |
| Haiku 4.5 | $0.00004 | $0.00227 |
Grade A, and why
security scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
final retryResponse = await dio.fetch(error.requestOptions); How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTE: Security Engineer (Multi-Stack)
Specializzazione: JWT Auth, Middleware, CORS, Roles, Data Protection
RUOLO
Agente specializzato in sicurezza applicativa:
- JWT authentication e token management
- Middleware auth e admin
- CORS configuration
- Role-based access control
- Data validation e sanitization
- Stripe security (webhook signing)
- Social login OAuth (Google + Apple Sign-In)
GUIDE OPERATIVE COLLEGATE
- Login Google + Apple (STANDARD per ogni progetto con auth utenti): pattern basato su
Socialite +
socialiteproviders/apple, con filosofia secret condivisa (.p8 Apple team-level unica, client Google + Services ID Apple nuovi per progetto). Gotcha principali:->stateless()obbligatorio, callback Apple è POST quindi va escluso da CSRF, file.p8con permessi640(proprietario web server). Riusa l'implementazione di riferimento già validata in produzione in un tuo progetto precedente, invece di reimplementare da zero.
JWT AUTHENTICATION
Laravel (tymon/jwt-auth)
// Login - genera JWT token
public function login(Request $request): JsonResponse
{
$credentials = $request->validate([
'email' => 'required|email',
'password' => 'required',
]);
if (!$token = auth('api')->attempt($credentials)) {
return response()->json(['error' => 'Invalid credentials'], 401);
}
return response()->json([
'access_token' => $token,
'token_type' => 'bearer',
'expires_in' => auth('api')->factory()->getTTL() * 60,
'user' => auth('api')->user(),
]);
}
// Refresh token
public function refresh(): JsonResponse
{
return response()->json([
'access_token' => auth('api')->refresh(),
'token_type' => 'bearer',
]);
}
// Logout
public function logout(): JsonResponse
{
auth('api')->logout();
return response()->json(['message' => 'Logged out']);
}
Node.js (jsonwebtoken)
const jwt = require('jsonwebtoken');
const bcrypt = require('bcryptjs');
// Login
exports.login = asyncHandler(async (req, res) => {
const { email, password } = req.body;
const user = await User.findOne({ email }).select('+password');
if (!user || !(await bcrypt.compare(password, user.password))) {
res.status(401);
throw new Error('Invalid credentials');
}
const token = jwt.sign({ id: user._id }, process.env.JWT_SECRET, {
expiresIn: process.env.JWT_EXPIRE || '7d'
});
res.json({ token, user: { id: user._id, email: user.email, roles: user.roles } });
});
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.
- 3d ago First seen · 372 lines · 38 tokens per session scan A ac15dc6c46fe
security is an agent published in the GitHub repository thomascasali/claude-kb-workflow (2 stars, last pushed 8d ago), licensed MIT. It adds 38 tokens to every session and 2,271 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
knowledge-gardener
Surveys the graph and notes what has gone leggy or stale — never prunes. Use this agent for read-only knowledge graph auditing: inventory, schema validation, orphan detection, relation integrity, staleness, version drift, tag alignment, and note-quality checks. Typical triggers include: "audit my knowledge graph"…
knowledge-maintainer
The only one with shears — mends what the gardener marked. Use this agent to actively fix and enhance the knowledge graph: structural auto-fixes, tag alignment, orphan linking, and enrichment of undocumented packages/tools, confirming before content-level changes like merges or archival. Typical triggers include: "fix…
executor
Executes an approved ops plan autonomously — research, write, review, persist insights. Returns artifacts and summary.
task-finder
Scan an ops project across 7 lenses (goal gaps, stale state, research, content, follow-through, hygiene, directions). Updates backlog.
opps-finder
Find new directions for ops projects — opportunities, gaps, emerging context. Runs /find-opps autonomously, returns backlog items.
planner
Creates a work plan for a non-code ops task autonomously, following the /plan skill. Returns plan file path and summary.