implement-feature

A command that implements a complete software feature from a Jira ticket or written requirements. It coordinates multiple agents during delivery.

In plain words
What is it for?
Use it for tickets such as TMS-320 or for other feature requirements that need implementation.
Why use it?
It helps turn a tracked requirement into a finished implementation without manually coordinating each development task.

Command

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 commands/wonjun3991/study/implement-feature
Clone the repo
git clone --depth 1 https://github.com/wonjun3991/study
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,732 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown 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.00030 $0.03732
Opus 5 $0.00015 $0.01866
Sonnet 5 $0.00006 $0.00746
Haiku 4.5 $0.00003 $0.00373

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

Security

Grade A, and why

implement-feature 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Check Jira API connection: `curl -s -o /dev/null -w "%{http_code}" -u "$JIRA_EMAIL:$JIRA_API_TOKEN" "$JIRA_BASE_URL/rest/api/2/myself"`
presentation/harness-engineering/reference/commands/implement-feature.md · 477 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 477 lines · 30 tokens per session scan A 00990ed6c1b3

Subscribe to this mod's changes

implement-feature is a command published in the GitHub repository wonjun3991/study (2 stars, last pushed 3mo ago), with no licence file. It adds 30 tokens to every session and 3,732 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.