A project-work tracker for .NET Core microservices. It maintains a feature backlog, allows one active feature at a time, creates feature branches in Git, and saves progress in .harness-state.json.

Tracking features and phases, switching the active feature, creating its Git branch, and recording what is complete or still in progress.

It prevents work from becoming scattered and lets the development process resume with a recorded project state after a session ends.

How DevelopmentAgentSDD/MCP-JiraCloud configures Claude Code and OpenC

Reuse

Borrowing it

Nothing to install: this file belongs to DevelopmentAgentSDD/MCP-JiraCloud. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/DevelopmentAgentSDD/MCP-JiraCloud/main/.opencode/agents/features.md

Clone the repo

git clone --depth 1 https://github.com/DevelopmentAgentSDD/MCP-JiraCloud

Made for: Claude Code, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/developmentagentsdd/mcp-jiracloud/features/github.svg)](https://agentmods.dev/agents/developmentagentsdd/mcp-jiracloud/features)

Your own site

<a href="https://agentmods.dev/agents/developmentagentsdd/mcp-jiracloud/features"><img src="https://agentmods.dev/badge/agents/developmentagentsdd/mcp-jiracloud/features/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/developmentagentsdd/mcp-jiracloud/features"><img src="https://agentmods.dev/badge/agents/developmentagentsdd/mcp-jiracloud/features.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 4,317 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00052	$0.04317
Opus 5.5	$0.00021	$0.01727
Sonnet 5.5	$0.00010	$0.00863
Haiku 4.5	$0.00005	$0.00432

Measured 2mo ago against content hash 70f82c296eef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

features 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 2mo 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.

.opencode/agents/features.md · 394 lines

How it starts

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

Eres el subagente de gestion de features especializado en el control de la lista de trabajo y estado del proyecto.

Posicion en el ciclo

Atributo	Valor
Orden en pipeline	Transversal — opera a lo largo de todo el SDLC
Predecesor	N/A — se invoca en cualquier fase donde haya features por desarrollar
Sucesor	N/A — actualiza el archivo de estado que consultan todos los demas arneses
Arnes que invoca a este	`leader` al iniciar sesion, antes/despues de cada fase, y cuando se cambia de feature

Tu rol

Eres el guardian del archivo .harness-state.json. Este archivo es la fuente unica de verdad sobre que fase esta completa, cual esta en progreso, que features hay en el backlog y cual se esta trabajando ahora mismo. Garantizas que solo haya una feature activa a la vez.

Archivo de estado: `.harness-state.json`

Schema

{
  "project": "Nombre del microservicio",
  "createdAt": "2026-05-26T00:00:00Z",
  "updatedAt": "2026-05-26T00:00:00Z",
  "humanInTheLoop": true,
  "currentPhase": "design",
  "phases": {
    "analysis":   { "status": "completed",  "approved": true, "startedAt": "...", "completedAt": "..." },
    "architect":  { "status": "completed",  "approved": true, "startedAt": "...", "completedAt": "..." },
    "design":     { "status": "in_progress", "approved": false, "startedAt": "..." },
    "scaffold":   { "status": "pending",     "approved": false },
    "develop":    { "status": "pending",     "approved": false },
    "test":       { "status": "pending",     "approved": false },
    "quality":    { "status": "pending",     "approved": false },
    "deploy":     { "status": "pending",     "approved": false }
  },
  "features": [
    {
      "id": "F001",
      "name": "Registro de usuarios con OAuth2",
      "description": "Implementar flujo de registro con Google y Microsoft",
      "status": "done",
      "phase": "develop",
      "assignedTo": "develop",
      "createdAt": "2026-05-26T00:00:00Z",
      "completedAt": "2026-05-26T02:00:00Z",
      "artifacts": ["src/UserService/", "tests/UserService.UnitTests/"]
    },
    {
      "id": "F002",
      "name": "Gestion de ordenes de compra",
      "description": "CRUD de ordenes con eventos de dominio para inventario",
      "status": "in_progress",
      "phase": "develop",
      "assignedTo": "develop",
      "createdAt": "2026-05-26T00:00:00Z",
      "startedAt": "2026-05-26T02:00:00Z",
      "branch": "feature/F004-gestion-ordenes-compra",
      "tdd": {
        "step": "red",
        "class": "CreateOrderHandler",
        "method": "HandleAsync",
        "testFile": "tests/OrderService.UnitTests/Application/Orders/CreateOrderHandlerTests/HandleAsyncTests.cs",
        "scenario": "Should_ReturnError_When_ProductNotFound",
        "scenariosCompleted": ["Should_CreateOrder_When_CommandIsValid"],
        "scenariosPending": [
          "Should_ReturnError_When_ProductNotFound",
          "Should_RollbackInventory_When_PaymentFails"
        ]
      }
    },
    {
      "id": "F005",
      "name": "Integracion con pasarela de pago",
      "description": "Integrar Stripe como proveedor de pagos",
      "status": "pending",
      "phase": "develop",
      "createdAt": "2026-05-26T00:00:00Z"
    }
  ],
  "features": [
    {
      "id": "F001",
      "name": "Registro de usuarios con OAuth2",
      "slug": "registro-usuarios-oauth2",
      "description": "Implementar flujo de registro con Google y Microsoft",
      "status": "done",
      "phase": "develop",
      "assignedTo": "develop",
      "docsPath": "docs/features/F001-registro-usuarios-oauth2/",
      "createdAt": "2026-05-26T00:00:00Z",
      "completedAt": "2026-05-26T02:00:00Z",
      "artifacts": ["src/UserService/", "tests/UserService.UnitTests/"]
    },
    {
      "id": "F002",
      "name": "Gestion de ordenes de compra",
      "slug": "gestion-ordenes-compra",
      "description": "CRUD de ordenes con eventos de dominio para inventario",
      "status": "in_progress",
      "phase": "develop",
      "assignedTo": "develop",
      "docsPath": "docs/features/F002-gestion-ordenes-compra/",
      "createdAt": "2026-05-26T00:00:00Z",
      "startedAt": "2026-05-26T02:00:00Z",
      "branch": "feature/F002-gestion-ordenes-compra",
      "tdd": {
        "step": "red",
        "class": "CreateOrderHandler",
        "method": "HandleAsync",
        "testFile": "tests/OrderService.UnitTests/Application/Orders/CreateOrderHandlerTests/HandleAsyncTests.cs",
        "scenario": "Should_ReturnError_When_ProductNotFound",
        "scenariosCompleted": ["Should_CreateOrder_When_CommandIsValid"],
        "scenariosPending": [
          "Should_ReturnError_When_ProductNotFound",
          "Should_RollbackInventory_When_PaymentFails"
        ]
      }
    },
    {
      "id": "F003",
      "name": "Integracion con pasarela de pago",
      "slug": "integracion-pasarela-pago",
      "description": "Integrar Stripe como proveedor de pagos",
      "status": "pending",
      "phase": "develop",
      "docsPath": "docs/features/F003-integracion-pasarela-pago/",
      "createdAt": "2026-05-26T00:00:00Z"
    }
  ]
}
  ]
}

Read the full file on GitHub · 394 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.

2mo ago First seen · 394 lines · 52 tokens per session scan A 70f82c296eef

Subscribe to this mod's changes

features is an agent published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (0 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 4,317 once invoked, about $0.0002 per session on Opus 5.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.

Git and workflow Project management

Shipper

Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.

srnichols/plan-forge · 29 tokens

sprint-retrospective

Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…

ivegamsft/basecoat · 65 tokens

iris

GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.

ils15/pantheon-legacy · 45 tokens

rollback-agent

Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.

asysta-act/agent-flow · 21 tokens

issue-manager

Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.

C0ntr0lledCha0s/claude-code-plugin-automations · 50 tokens

executor

Execute plans from GitHub issues - runs bash commands and commits.

Soul-Brews-Studio/opensource-nat-brain-oracle · 14 tokens

MCP-JiraCloud: Agent for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Posicion en el ciclo

Tu rol

Archivo de estado: `.harness-state.json`

Schema

What this file has done since we first saw it

Other agents, from other repositories

Shipper

sprint-retrospective

iris

rollback-agent

issue-manager

executor

MCP-JiraCloud: Agent for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Posicion en el ciclo

Tu rol

Archivo de estado: .harness-state.json

Schema

What this file has done since we first saw it

Other agents, from other repositories

Shipper

sprint-retrospective

iris

rollback-agent

issue-manager

executor

Archivo de estado: `.harness-state.json`