Borrowing it
Nothing to install: this file belongs to alexeyleshchenko/fast-mcp-telegram. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alexeyleshchenko/fast-mcp-telegram/master/.cursor/skills/feature-development/SKILL.mdgit clone --depth 1 https://github.com/alexeyleshchenko/fast-mcp-telegramWrote 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/skills/alexeyleshchenko/fast-mcp-telegram/feature-development)<a href="https://agentmods.dev/skills/alexeyleshchenko/fast-mcp-telegram/feature-development"><img src="https://agentmods.dev/badge/skills/alexeyleshchenko/fast-mcp-telegram/feature-development/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.
<a href="https://agentmods.dev/skills/alexeyleshchenko/fast-mcp-telegram/feature-development"><img src="https://agentmods.dev/badge/skills/alexeyleshchenko/fast-mcp-telegram/feature-development.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.01147 |
| Opus 5 | $0.00014 | $0.00574 |
| Sonnet 5 | $0.00006 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
feature-development 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 9d 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.
This is a copy
100% identical to feature-development — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development Workflow
Process Overview
Research -> Plan -> Spike -> Implement -> Test -> Clean Up -> Push
Phase 1: Research
Goal: Understand the problem space and existing code
-
Explore codebase with explore subagent:
- Find relevant existing functions and patterns
- Understand data structures and type definitions
- Map relationships between components
-
API Investigation:
- Use Context7 MCP for library documentation
- Use WebSearch for Telegram API specs
- Use telegram-dev MCP for live API probing
- Verify actual return values and structures
-
Edge Case Identification:
- Identify potential issues early
- Note API limitations or quirks
- Check for existing tests that may break
Phase 2: Planning
Goal: Create a detailed, actionable plan
-
Clarify Requirements:
- Ask user for specifics on behavior
- Offer numbered options for implementation choices
- Default to simplest approach
-
Document Technical Findings:
- API behavior verified through research
- Type structures and field access patterns
- Known limitations and edge cases
-
Create Plan (use CreatePlan tool):
- Numbered steps with specific file:line references
- Code snippets for key changes
- Mermaid diagrams for complex relationships
- Complexity assessment table
Phase 3: Spiking
Goal: Verify assumptions with live API tests
Use telegram-dev MCP for live testing:
-
API Response Structure:
- Call methods directly and inspect raw responses
- Verify type definitions (e.g.,
TextWithEntitiesvs plain string) - Check field names and access patterns
-
Edge Cases:
- Test with edge cases (empty results, invalid inputs)
- Verify error handling behavior
- Confirm caching behavior if applicable
-
Document Findings:
- Update plan with corrected assumptions
- Note any API quirks or bugs
- Identify potential issues before implementation
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.
- 9d ago First seen · 211 lines · 28 tokens per session scan A 1bb309cb9296
feature-development is a skill published in the GitHub repository alexeyleshchenko/fast-mcp-telegram (2 stars, last pushed 19d ago), licensed MIT. It adds 28 tokens to every session and 1,147 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to feature-development, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pytdbot
Write Telegram bots and userbots with Pytdbot (async TDLib wrapper with high-level helpers; not the Telegram Bot API). Use when the user works with Pytdbot, TDLib, or pytdbot.Client.
langbot-dev
Develop, build, and debug the LangBot core backend and web frontend. Use when working inside the LangBot repository — backend (Python/Quart, src/langbot/pkg), the Vite/React web UI, HTTP API controllers/services, Alembic migrations, or the MCP server. Covers the dev environment (uv, pnpm), repo layout, the API auth…
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
api-services
API reference for built-in service providers (LLM, Speech, Graph). Use when looking up service interfaces, provider capabilities, or integration patterns.