agentmods.dev

feature

A workflow for adding a new capability to the Terfyn codebase. It covers reading the design, making the code change, adding tests, running checks, and updating release notes when needed.

In plain words
What is it for?
Use it when implementing a new command, behavior, or enhancement in the repository, including its tests and documentation.
Why use it?
It provides project-specific guidance so a feature fits the existing code and is checked before being considered complete. It also reduces unrelated changes.

Skill for Claude CodeCodexCursor

4 2d ago A scan 39 tokens original Apache-2.0
View the source file LAA-Software-Engineering/terfyn
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 skills/laa-software-engineering/terfyn/feature
Any agent
npx skills add LAA-Software-Engineering/terfyn --skill feature
Clone the repo
git clone --depth 1 https://github.com/LAA-Software-Engineering/terfyn

Made for: Claude Code, Codex, Cursor.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 353 The whole file, excluding the scripts and references it only reads on demand.
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.00039 $0.00353
Opus 5 $0.00019 $0.00177
Sonnet 5 $0.00008 $0.00071
Haiku 4.5 $0.00004 $0.00035

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

Security

Grade A, and why

feature 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 2d 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.

.cursor/skills/feature/SKILL.md · 27 lines

What it actually says

Feature

Workflow

  1. Clarify scope — Read docs/DESIGN_DOC.md and nearby code before coding. Prefer the smallest change that meets the ask.
  2. Implement — Match patterns in the same package (cmd/terfyn, internal/*). Avoid unrelated refactors.
  3. Tests — Add or update unit/integration coverage. For intentional CLI output changes: GO_UPDATE_GOLDEN=1 go test ./internal/cli/... -run TestGolden_
  4. Verify — Run make ci (verify-fmt, vet, test). Fix failures before claiming done.
  5. Changelog — If user-visible or breaking, add an entry under Unreleased in CHANGELOG.md.
  6. Pull request — When opening a PR, read .github/PULL_REQUEST_TEMPLATE.md and use that exact structure for the body (HEREDOC with gh pr create). Fill Summary, Test plan, and Checklist. Do not invent a different format.

Layout reminders

Area Path
CLI entry cmd/terfyn
Commands / goldens internal/cli
Spec / project load internal/spec, internal/project
Plan / apply / engine / policy internal/plan, internal/apply, internal/engine, internal/policy
E2E test/integration
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. 2d ago First seen · 27 lines · 39 tokens per session scan A af1ac2653702

Subscribe to this mod's changes

feature is a skill published in the GitHub repository LAA-Software-Engineering/terfyn (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 39 tokens to every session and 353 once invoked, about $0.0002 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.

Data and AIGit and workflowTestingagentsai-agentsclideclarativegitopsgolang
Related

Other skills, from other repositories

qa-find-bugs

Drive the live product at https://dashboard.bex.co as a signed-in QA user (QAEMAIL / QAPASSWORD from .env), hunt real bugs across the hosting features, research each fix down to file:line, file the non-duplicate findings to the w6 board through /pm, and /ship the scheduled milestone. Use when the user asks to QA the…

bex-co/bex · 96 tokens

pm

Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.

bex-co/bex · 48 tokens

stripe-projects

Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set…

bex-co/bex · 213 tokens

deploy-app-from-local

Deploy a local checkout to a production Hetzner App using the manual image-import runbook. Use when the user asks to ship local working-tree code to a live bex App rather than deploy from remote Git. Arguments are the local repo path and app name.

bex-co/bex · 58 tokens

ship

Safely bring main up to date, commit intended pending changes, and push to origin/main. Use when the user explicitly asks to ship the current main branch or invokes the repository's ship workflow.

bex-co/bex · 41 tokens

mock-cluster

Stand up or scale the local CAPD mock cluster and deploy the bex operator into it. Use when the user asks to create, inspect, or resize the repository's local development cluster. Optional argument: scale N.

bex-co/bex · 48 tokens