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.
npx agentmods add commands/konnexx-software-developers/konnexx-dev-mcp/implement-featuregit clone --depth 1 https://github.com/Konnexx-Software-Developers/konnexx-dev-mcpWrote 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.
[](https://agentmods.dev/commands/konnexx-software-developers/konnexx-dev-mcp/implement-feature)<a href="https://agentmods.dev/commands/konnexx-software-developers/konnexx-dev-mcp/implement-feature"><img src="https://agentmods.dev/badge/commands/konnexx-software-developers/konnexx-dev-mcp/implement-feature.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.01375 |
| Opus 5 | $0.00000 | $0.00687 |
| Sonnet 5 | $0.00000 | $0.00275 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
implement-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Feature (MCP Package Development)
You are a feature implementation assistant for the konnexx-dev-mcp package. Use this command to add new features, commands, or improvements to the MCP server.
How to Use This Command
In Cursor chat, type:
Use implement-feature
Feature: [Describe the feature you want to add]
Example:
Use implement-feature
Feature: Add a new shared command for database migrations that uses Database MCP to verify migration syntax before committing.
Workflow
Step 1: Understand Requirements
Analyze the feature request:
- What type of feature? (New command, tool enhancement, bug fix, etc.)
- Which project type does it affect? (shared, api, web, architecture, mobile)
- Does it require new MCP integrations?
- What files need to be created/modified?
Step 2: Plan Implementation
Create an implementation plan:
-
File Structure:
- New command files in
commands/{type}/ - Updates to
src/index.tsif adding tools - Test files in
src/*.test.ts - Documentation if needed
- New command files in
-
Implementation Steps:
- Create command markdown file
- Add tool definition to
src/index.ts - Add command mapping
- Write tests
- Update README if needed
-
Testing Strategy:
- Unit tests for new functions
- Integration tests for command loading
- Verify tool appears correctly
Step 3: Implement
For New Commands:
-
Create command file:
- Location:
commands/{type}/{command-name}.md - Use kebab-case for filename
- Follow existing command structure (Overview, Usage, Steps, etc.)
- Location:
-
Add tool to
src/index.ts:- Add tool definition in appropriate
*Toolsarray - Add description following pattern: "Execute complete [workflow] following team standards..."
- Add to
commandMapin tool handler
- Add tool definition in appropriate
-
Write tests:
- Add to
src/commands.test.tsto verify file exists - Add to
src/command-integration.test.tsto verify loading - Add specific tests if needed
- Add to
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.
- 5d ago First seen · 227 lines · 0 tokens per session scan A a0b45f760440
implement-feature is a command published in the GitHub repository Konnexx-Software-Developers/konnexx-dev-mcp (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,375 tokens. 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.