tend AGENTS.md

A set of repository instructions for the tend skill pack, which contains on-demand maintenance skills for SvelteKit and TypeScript projects. It defines the project layout, shared configuration, and safe way to make changes.

In plain words
What is it for?
Use it when maintaining the tend skill pack, adding or editing skills, judging changes, or following its scan-and-verify workflow.
Why use it?
It gives contributors consistent rules for creating reliable, minimal fixes that a stranger can safely use in their own repository.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/robcsaszar/tend/agents-md
Clone the repo
git clone --depth 1 https://github.com/robcsaszar/tend

Made for: Codex, OpenCode.

Per session 1,098 This file is loaded in full into every session.
When invoked 1,098 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01098 $0.01098
Opus 5 $0.00549 $0.00549
Sonnet 5 $0.00220 $0.00220
Haiku 4.5 $0.00110 $0.00110

Measured yesterday against content hash b0d7e7969d6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tend AGENTS.md 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 yesterday.

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.

AGENTS.md · 38 lines

How it starts

The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Mission

This repo publishes the tend skill pack: local, on-demand maintenance skills for SvelteKit + TypeScript repos. There is no build, no tests, no runtime of its own. The deliverable is the contents of skills/*. Every skill shares one shape (config → triage → scan → fix → verify, one atomic change per run, never commit) and one shared config file (.claude/tend/config.yaml, schema owned by tend-onboard). Changes should be judged by: would a stranger who installs one of these skills into their own SvelteKit repo get a correct, safe, minimal fix out of it?

Layout convention

  • One directory per skill under skills/<name>/, name: in frontmatter matching the directory name exactly.
  • Every skill follows the same phase structure: 0. Load config1. Triage (MANDATORY READ a core reference) → 2. Scan (stop at first real hit; module-gated checks load only when their module is active) → 3. Fix (one atomic, verified change) → 4. Verify & present (re-run checks, show diff, never commit) → ## NEVER (3-line **NEVER**/**Instead:**/**Why:** format). Keep new skills or edits to existing ones in this shape: it's load-bearing, not decorative; tend-onboard's config schema and every other skill's Phase 0 wording assume it.
  • Structured-findings skills (tend-security, tend-refactor, tend-tests) ship scripts/validate-*.mjs + assets/*.json. Diff-is-the-finding skills (tend-perf, tend-a11y, tend-docs) don't. Don't add a validator to one of these without updating this file's reasoning for why not.
  • Every skill ships evals/eval-N/{prompt,assertions}.md. See ai-forge-eval in the source repo (orakl) for the assertion format if extending.
  • Every skill sets disable-model-invocation: true in frontmatter: user-invoked only (/tend-security, etc.), never auto-triggered from conversation. This is the design decision behind the whole pack (single-skill, on-demand, human-paced runs replacing an unattended CI fleet that produced an 84-PR backlog). A skill that auto-triggers reintroduces the unattended-breadth failure mode the pack exists to avoid. New skills must set this flag too; don't add trigger-phrase language to a description once this flag is set, it's dead weight since auto-matching never runs.
  • skills/tend-onboard/assets/tend-sweep.yml is a copy-out template for consuming repos, installed (opt-in, cadence-adjusted) by tend-onboard's Phase 4. .github/workflows/ in this repo stays empty by design — never turn the template into a live workflow here.

Read the full file on GitHub · 38 lines

Changes

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.

  1. yesterday First seen · 38 lines · 1,098 tokens per session scan A b0d7e7969d6e

Subscribe to this mod's changes

tend AGENTS.md is an instructions file published in the GitHub repository robcsaszar/tend (0 stars, last pushed 2d ago), licensed MIT. It adds 1,098 tokens to every session, about $0.0055 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.