Edt MCP Architecture
DitriXNew/EDT-MCP
Map of the EDT-MCP plugin's target architecture — where the shared helpers live, the layering rules, and the canonical way to do project/metadata/code resolution.
Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists.
Install Harness Engineering Lifecycle
$ npx skills add Arenukvern/mcp_flutter --skill harness-engineering-lifecycle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Arenukvern/mcp_flutter harness-engineering-lifecycle --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/harness-engineering-lifecycle .claude/skills/harness-engineering-lifecycle && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "harness-engineering-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/harness-engineering-lifecycle into .claude/skills/harness-engineering-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "harness-engineering-lifecycle", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/harness-engineering-lifecycleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Arenukvern/mcp_flutter --skill harness-engineering-lifecycle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Arenukvern/mcp_flutter harness-engineering-lifecycle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/harness-engineering-lifecycle .agents/skills/harness-engineering-lifecycle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "harness-engineering-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/harness-engineering-lifecycle into .agents/skills/harness-engineering-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "harness-engineering-lifecycle", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Arenukvern/mcp_flutter --skill harness-engineering-lifecycle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Arenukvern/mcp_flutter harness-engineering-lifecycle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/harness-engineering-lifecycle .cursor/skills/harness-engineering-lifecycle && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "harness-engineering-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/harness-engineering-lifecycle into .cursor/skills/harness-engineering-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "harness-engineering-lifecycle", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Arenukvern/mcp_flutter.git --path .agents/skills/harness-engineering-lifecycle--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Arenukvern/mcp_flutter --skill harness-engineering-lifecycle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Arenukvern/mcp_flutter harness-engineering-lifecycle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/harness-engineering-lifecycle .gemini/skills/harness-engineering-lifecycle && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "harness-engineering-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/harness-engineering-lifecycle into .gemini/skills/harness-engineering-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "harness-engineering-lifecycle", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Arenukvern/mcp_flutter harness-engineering-lifecycleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Arenukvern/mcp_flutter --skill harness-engineering-lifecycle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/harness-engineering-lifecycle .github/skills/harness-engineering-lifecycle && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "harness-engineering-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/harness-engineering-lifecycle into .github/skills/harness-engineering-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "harness-engineering-lifecycle", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Arenukvern/mcp_flutter --skill harness-engineering-lifecycle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Arenukvern/mcp_flutter harness-engineering-lifecycle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/harness-engineering-lifecycle .opencode/skills/harness-engineering-lifecycle && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "harness-engineering-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/harness-engineering-lifecycle into .opencode/skills/harness-engineering-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "harness-engineering-lifecycle", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
harness-engineering-lifecycle- GitHub stars
- 386
- Token cost
- ~1.6k tokens
- SKILL.md length
- 777 words
- Files
- 5 (incl. references)
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists.
- Works in 4 steps: Layer 0 (The Embedded Agent Surface):… → Layer 1 (The Protocol Adapter): Build… → Layer 2 (The Orchestrator): Build… → …
- Refactoring custom validation CLIs/MCPs for large polyrepos
- SKILL.md covers When to use, When not to use, Part 1: The Cascading Agent… and Part 2: Cross-Repo Remediation…, plus 3 more sections
- Calls npx
What it does
Harness Engineering Lifecycle is an agent skill from Arenukvern/mcp_flutter. Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists. Use when refactoring custom validation CLIs/MCPs for large polyrepos, extending Steward across sibling repos, or deploying a local tool to a consumer project for dogfooding and testing; use mcp-harness-repo-maintainer first for initial steward.yaml adoption and cold-start proof.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/cases/first-action-dormant.yaml`, `evals/cases/producer-consumer-trigger.yaml` and `references/evals.md`).
It sits in Agent Workflows, covering MCP servers and Refactoring. It works with Model Context Protocol. The repository describes itself as: MCP Toolkit for Flutter AI Agent Driven Development (MCP/CLI + custom client side tools) - via closed feedback loop (visual & semantic snapshot) and high client side… The licence is MIT.
When your agent uses it
- Refactoring custom validation CLIs/MCPs for large polyrepos
- Extending Steward across sibling repos
- Deploying a local tool to a consumer project for dogfooding and testing
- Use mcp-harness-repo-maintainer first for initial steward.yaml adoption and cold-start proof
Example prompts
- “/harness-engineering-lifecycle”
Requirements
- Node.js
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Layer 0 (The Embedded Agent Surface): The target application or engine must natively expose its internal state via explicit hooks (e.g…
- Layer 1 (The Protocol Adapter): Build generalized MCP servers or protocol adapters to connect to Layer 0. These tools provide raw…
- Layer 2 (The Orchestrator): Build specialized harness CLIs that use their own automation/scripting to chain multiple Layer 1 actions…
- Layer 3 (The AI Wrapper): Following the agentskills.io spec, Skills can and should contain thin-wrapper tools (scripts). The Skill acts as…
What it can do on your machine
Read from SKILL.md and the folder at commit 62f3ee1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Harness Engineering Lifecycle loads about 1.6k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 113 tokens; SKILL.md has 777 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Arenukvern/mcp_flutter at commit 62f3ee1, republished under its MIT licence (© Arenukvern). 777 words, ~1,626 tokens.
Download SKILL.mdSave it as
.claude/skills/harness-engineering-lifecycle/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- harness-engineering-lifecycle
- description
- Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists. Use when refactoring custom validation CLIs/MCPs for large polyrepos, extending Steward across sibling repos, or deploying a local tool to a consumer project for dogfooding and testing; use mcp-harness-repo-maintainer first for initial steward.yaml adoption and cold-start proof.
- license
- MIT
- type
- governance
- metadata.author
- skill-steward
- metadata.version
- 1.1.0
- metadata.category
- harness
Harness Engineering Lifecycle
Evolve a proven repo-local contract into a generalized, high-performance, declarative harness system, then safely dogfood those changes across a producer-consumer repository boundary. Start here only after the target repo has a steward.yaml contract and at least an H2 smoke proof; use mcp-harness-repo-maintainer before that.
When to use
- Evolving custom validation scripts into a central linter engine.
- Extending
stewardCLI features for large polyrepos. - Testing a local CLI/harness build against a sibling repository to catch path-resolution crashes or integration friction.
- Turning repeated local benchmark/probe findings into a reusable harness feature.
When not to use
- Initial
steward.yamladoption or first quick probe in one repo — usemcp-harness-repo-maintainer. - Skill creation, registry updates, or marketplace packaging — use
skill-authoring-lifecycleorplugin-marketplace-setup. - Product-specific diagnostics before a cold-start contract exists — first add a bounded action, probe, and scenario in the target repo.
Part 1: The Cascading Agent Surface (Architecture & Generalization)
When engineering a harness beyond one local contract, follow the Cascading Agent Surface guidelines. A strict separation of tools vs skills can fail once repo workflows span multiple packages, adapters, or consumers. Instead, link them using domain-agnostic abstractions:
- Layer 0 (The Embedded Agent Surface): The target application or engine must natively expose its internal state via explicit hooks (e.g., RPC or memory probes). Do not rely on brittle UI scraping or black-box testing.
- Layer 1 (The Protocol Adapter): Build generalized MCP servers or protocol adapters to connect to Layer 0. These tools provide raw visibility and actuation (e.g., taking screenshots, reading memory) but must contain NO business logic.
- Layer 2 (The Orchestrator): Build specialized harness CLIs that use their own automation/scripting to chain multiple Layer 1 actions together. The Orchestrator's primary job is the Fast Feedback Loop: it must emit structured, diagnostic JSON to pinpoint exactly what broke across boundaries.
- Layer 3 (The AI Wrapper): Following the
agentskills.iospec, Skills can and should contain thin-wrapper tools (scripts). The Skill acts as the AI's brain: it teaches the AI how to trigger Layer 2, interpret its complex JSON heuristics, and safely execute domain-specific recovery tools.
Generalization Principles
- Decouple transport from engine: Command interfaces (CLI) and JSON-RPC (MCP) are thin wrappers. All logic lives in a reusable core package.
- Declarative configuration: Use a configuration file (like
steward.yaml) to specify:- Branding: Name and description of the harness.
- Actions: Typed, bounded repo-local commands with effects, limits, outputs, and evidence policy.
- Documentation lattice: Maps of labels to specific doc files.
- Pruned traversals: Never perform recursive file-walking (
list(recursive: true)) without pruning standard build/VCS folders early. - Generalized checks: Do not hardcode linters. Use parameterized declarative engines (e.g.
disallowed-substrings).
Show full SKILL.md (342 more words)Show less
Part 2: Cross-Repo Remediation (Testing)
When you make changes to the harness (Producer), you must validate it against dependent downstream projects (Consumer).
- Establish Sibling Baseline: Locate the consumer repository (e.g.
../<consumer-repo-name>). Run its tests to ensure it starts green. Do not change it yet. - Deploy Local Producer: Build and install the local development version of your harness.
- Capture Adoption Friction: Run the consumer's validation suite using the local producer build. Document path crashes or fragile rules in a scratchpad.
- Core Remediation: Fix the root causes in the Producer codebase. Generalize the fix; do not write consumer-specific hacks.
- Consumer Configuration Remediation: Update the Consumer repository to leverage the new generalized features (e.g. updating its
steward.yaml). - Dual Verification: Verify that the consumer suite passes, and the producer suite passes.
- Durable Knowledge: Extract any learnings to ADRs or FAQs using the
repository-governance-lifecycleskill.
Detour stop rule: If installing, activating, or wiring the local producer build fails twice, stop restoration, record the friction, use the consumer's native gate or portable fallback when possible, and return to the original acceptance check. Do not promote a generalized harness capability from that same detour; capture an observation or unknown case first.
Producer/consumer proof artifacts
Before promoting a generalized harness change, capture the proof from both sides.
| Side | Required artifact | Purpose |
|---|---|---|
| Producer | Changed schema/action/rule with tests or validator output | Shows the generalized feature works in the source harness. |
| Consumer | Updated steward.yaml or scenario manifest | Shows adoption does not require local-path magic. |
| Consumer | Benchmark summary or truthful durability_blocked output | Shows a fresh agent can see what is proven and what is blocked. |
| Both | Validation commands and versions | Makes failures reproducible across repos. |
| Docs | ADR/FAQ update when the boundary changed | Keeps future agents from rediscovering the same split. |
Do not promote a local fix into the generalized harness when only one consumer has a private path workaround. Keep it local until the contract, schema, or rule has a reusable shape and at least one held-out or future-agent repeat proves it transfers.
Install
npx skills add arenukvern/skill_steward --skill harness-engineering-lifecycleSources
© Arenukvern, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in .agents/skills/harness-engineering-lifecycle of Arenukvern/mcp_flutter.
- SKILL.md
- evals/cases/first-action-dormant.yaml
- evals/cases/producer-consumer-trigger.yaml
- references/evals.md
- references/sources.md
Open the folder on GitHubat commit 62f3ee1
Compare with similar skills
Harness Engineering Lifecycle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Harness Engineering Lifecycle this skillArenukvern/mcp_flutter | 386 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Edt MCP ArchitectureDitriXNew/EDT-MCP | 295 | — | ~1.2k | Automated safety check: Pass | AGPL-3.0 | |
| Memtrace Decision Memorysyncable-dev/memtrace-public | 489 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Testing With API Mocksstacklok/toolhive-studio | 170 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Flow SwarmLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.3k | Automated safety check: Pass | MIT | |
| Edt MCP Project Local FixDitriXNew/EDT-MCP | 295 | — | ~507 | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Memtrace Decision Memory
syncable-dev/memtrace-public
Use Cortex decision memory through the normal Memtrace MCP tools.
Testing With API Mocks
stacklok/toolhive-studio
Start here for all API mocking in tests. An agent skill from stacklok/toolhive-studio.
Flow Swarm
LeoYeAI/openclaw-master-skills
Multi-agent swarm orchestration via RuFlo + Claude Code. An agent skill from LeoYeAI/openclaw-master-skills.
Edt MCP Project Local Fix
DitriXNew/EDT-MCP
Apply one bounded BSL correction through EDT-MCP with lost-update protection, targeted validation, and minimal diff.
Roslynk
mrpmorris/Roslynk
How to use the Roslynk MCP tools (mcproslynk) effectively for .NET work.
More from Arenukvern/mcp_flutter
All 23 skills in this repoMixture Of Experts
Arenukvern/mcp_flutter
Run a Mixture of Experts (MoE) audit on any topic, plan, codebase, evidence archive, or process.
Multi Agent Handoff
Arenukvern/mcp_flutter
Plan and document handoffs, parent lane contracts, and parallel batch contracts between specialized AI agents (foreman, workers, reviewers).
Plugin Marketplace Setup
Arenukvern/mcp_flutter
Designs public or private Agent Skill and plugin marketplaces for Cursor, Claude Code, Codex, Zed, Open Plugin, and npx skills—manifest layout, install matrix, and Skill Steward vs product boundaries.
Release Changelog Harness
Arenukvern/mcp_flutter
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable.
Repository Governance Lifecycle
Arenukvern/mcp_flutter
Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks.
Skill Authoring Lifecycle
Arenukvern/mcp_flutter
Scaffold and formally review a new Agent Skill in this marketplace repo.
Related
Works with
Categories
Questions about Harness Engineering Lifecycle
What does Harness Engineering Lifecycle do?
Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists. Harness Engineering Lifecycle is an agent skill from Arenukvern/mcp_flutter. Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists.
When should I use Harness Engineering Lifecycle?
Harness Engineering Lifecycle fits situations like: refactoring custom validation CLIs/MCPs for large polyrepos; extending Steward across sibling repos; deploying a local tool to a consumer project for dogfooding and testing; use mcp-harness-repo-maintainer first for initial steward.yaml adoption and cold-start proof.
How do I install Harness Engineering Lifecycle in Claude Code?
Run `npx skills add Arenukvern/mcp_flutter --skill harness-engineering-lifecycle -a claude-code`. Or copy the skill folder (.agents/skills/harness-engineering-lifecycle in Arenukvern/mcp_flutter) into .claude/skills/harness-engineering-lifecycle in your project. Claude Code loads it when a task matches its description.
How do I install Harness Engineering Lifecycle in Codex?
Run `npx skills add Arenukvern/mcp_flutter --skill harness-engineering-lifecycle -a codex`. Or copy the skill folder (.agents/skills/harness-engineering-lifecycle in Arenukvern/mcp_flutter) into .agents/skills/harness-engineering-lifecycle in your project. Codex loads it when a task matches its description.
Can I use Harness Engineering Lifecycle in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Arenukvern/mcp_flutter --skill harness-engineering-lifecycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/harness-engineering-lifecycle, .gemini/skills/harness-engineering-lifecycle, .github/skills/harness-engineering-lifecycle and .opencode/skills/harness-engineering-lifecycle in your project.
What does Harness Engineering Lifecycle need to run?
Going by SKILL.md and its folder, Harness Engineering Lifecycle needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Harness Engineering Lifecycle access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Harness Engineering Lifecycle safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Harness Engineering Lifecycle use?
Harness Engineering Lifecycle is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Harness Engineering Lifecycle use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 271 tokens, read only when the agent opens those files.
What are the alternatives to Harness Engineering Lifecycle?
Skills that share tags, products or a category with Harness Engineering Lifecycle: Edt MCP Architecture (DitriXNew/EDT-MCP, 295 stars), Memtrace Decision Memory (syncable-dev/memtrace-public, 489 stars), Testing With API Mocks (stacklok/toolhive-studio, 170 stars) and Flow Swarm (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Harness Engineering Lifecycle?
Arenukvern (a GitHub user) maintains it in Arenukvern/mcp_flutter, which has 386 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 3, 2026.
Source: Arenukvern/mcp_flutter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.