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 skills/robcsaszar/tend/tend-securitynpx skills add robcsaszar/tend --skill tend-securitygit clone --depth 1 https://github.com/robcsaszar/tendWrote 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/skills/robcsaszar/tend/tend-security)<a href="https://agentmods.dev/skills/robcsaszar/tend/tend-security"><img src="https://agentmods.dev/badge/skills/robcsaszar/tend/tend-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.00132 | $0.01189 |
| Opus 5 | $0.00066 | $0.00594 |
| Sonnet 5 | $0.00026 | $0.00238 |
| Haiku 4.5 | $0.00013 | $0.00119 |
Grade A, and why
tend-security 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tend Security — the Sentinel
Find the single highest-priority security issue in this repo, fix it minimally, verify, and hand the diff back for review. One issue per run.
0. Load config
- Read
.claude/tend/config.yaml. Useskills.security(off-limits globs,notes) + themodules:list. - No config? Run at core tier: core SvelteKit + TS assumptions, no modules, conservative built-in off-limits (never touch lockfiles, CI,
.env, config). Emit once: "runtend-onboardto sharpen." Continue. - Active modules gate which reference packs load in Phase 2 (progressive disclosure).
1. Triage
MANDATORY READ references/scan-core.md.
Establish: active modules (from config), off-limits set (config globs + built-in rails), and the repo's auth/validation entry points.
2. Scan — priority order, stop at the first real hit
Core (always): {@html}/XSS on user data, hardcoded secrets, missing authz on protected endpoints, secrets in logs/responses, CSP hygiene.
Module checks — load a module's reference pack only if its module is active:
auth→references/module-auth.md—timingSafeEqualvs!==, token-in-DTO leak, IDOR via pass-through auth, XFF vs CF-Connecting-IPvalidation→references/module-validation.md— missing length-caps/maxItems,LIMIT -1, amplificationrealtime→references/module-realtime.md— credential-in-broadcast, amplificationdata→references/module-data.mdfeature-flags→references/module-flags.md— UI-gated ≠ backend-gated
Select exactly ONE highest-priority issue. STOP scanning once selected.
3. Fix — one atomic change
Answer all three before editing: (1) exact file:line, (2) concrete exploit path, (3) the minimal fix. Can't answer all → skip it, find another (or stop).
- Record baseline: run
typecheck+lint+ the affected tests. - Apply the single change (< 50 lines). Add a code comment at the change site naming the risk.
- Never alter auth/authz logic or public API contracts — flag instead.
What ships with it
14 files beside SKILL.md 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.
- assets/finding-schema.json 1.8 KB
- evals/eval-1/assertions.md 718 B
- evals/eval-1/prompt.md 101 B
- evals/eval-2/assertions.md 796 B
- evals/eval-2/prompt.md 269 B
- evals/eval-3/assertions.md 853 B
- evals/eval-3/prompt.md 97 B
- references/module-auth.md 6.7 KB
- references/module-data.md 2.6 KB
- references/module-flags.md 3.1 KB
- references/module-realtime.md 4.7 KB
- references/module-validation.md 6.6 KB
- references/scan-core.md 8.8 KB
- scripts/validate-finding.mjs 5.9 KB runs code
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 · 65 lines · 132 tokens per session scan A 59188ea7d14c
tend-security is a skill published in the GitHub repository robcsaszar/tend (0 stars, last pushed 4d ago), licensed MIT. It adds 132 tokens to every session and 1,189 once invoked, about $0.0007 per session on Opus 5. 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 skills, from other repositories
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
simplify-codebase
Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any…
cyclomatic-complexity
Refactor code to reduce cyclomatic complexity so it stays readable, maintainable, and aligned with the long-term vision of the codebase, not just optimized for AI comprehension. Use whenever the user asks to refactor, simplify, clean up, or review code quality; mentions complexity, maintainability, readability…
refactor
Refactor code to improve structure and maintainability.
absolute-simplify
Use when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on…
techdebt
Find and fix technical debt including duplicated code, dead code, outdated patterns, and code smells. Run at the end of sessions to clean up.