Borrowing it
Nothing to install: this file belongs to MarcoAR1/botuyo-mcp. 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/MarcoAR1/botuyo-mcp/main/.agents/skills/botuyo-mcp-conventions/SKILL.mdgit clone --depth 1 https://github.com/MarcoAR1/botuyo-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/skills/marcoar1/botuyo-mcp/botuyo-mcp-conventions)<a href="https://agentmods.dev/skills/marcoar1/botuyo-mcp/botuyo-mcp-conventions"><img src="https://agentmods.dev/badge/skills/marcoar1/botuyo-mcp/botuyo-mcp-conventions/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/marcoar1/botuyo-mcp/botuyo-mcp-conventions"><img src="https://agentmods.dev/badge/skills/marcoar1/botuyo-mcp/botuyo-mcp-conventions.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.00038 | $0.01943 |
| Opus 5 | $0.00019 | $0.00971 |
| Sonnet 5 | $0.00008 | $0.00389 |
| Haiku 4.5 | $0.00004 | $0.00194 |
Grade A, and why
BotUyo MCP Architecture and Testing Rules 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 11d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BotUyo MCP Server — Hard Rules & Architecture
READ THIS ENTIRE FILE before making changes to the codebase. These are immutable rules that MUST be followed.
Core stack: TypeScript (strict) · Node.js (native fetch) · @modelcontextprotocol/sdk · Zod · Vitest
Module system: ESM ("type": "module") — all import paths MUST use .js extension
Published as: @botuyo/mcp on npm
RULE 0: Scope — Exclusive Responsibility (DO NOT MIX)
@botuyo/mcp exists SOLELY to build and configure conversational AGENTS
(agents, families, stages, tools, knowledge, avatars, templates, publishing).
- NEVER add Recruiting tooling here (org profile, vacancy templates, presets, pipelines, candidates, reports, etc.). Recruiting is a separate, isolated product with its own auth/tenant model.
- ALL conversational configuration of the Recruiting product is owned by the Recruiting copiloto, NOT by this agent-building MCP.
- Do NOT create
configure_recruiting_*,create_vacancy_template,apply_recruiting_presetor any recruiting tool/command in this repo.
RULE 1: Project Architecture
src/
├── index.ts # Entry point: CLI sub-command router + MCP server startup
├── client.ts # BotuyoApiClient — thin HTTP wrapper (GET/POST/PUT/DELETE)
├── tools/ # MCP tool definitions + handlers (one file per tool)
│ ├── index.ts # Registry: ALL_TOOLS[] + TOOL_HANDLERS{}
│ ├── {tool}.ts # Each tool: definition const + handler function
│ └── __tests__/ # One .spec.ts per tool (MockClient pattern)
└── commands/ # CLI sub-commands (login, auth, tenants, setup, etc.)
Hard rules:
src/tools/= MCP tools (exposed to AI assistants)src/commands/= CLI commands (exposed to human users)dist/= compiled output — NEVER edit manually
RULE 2: Tool File Pattern (CRITICAL)
Every MCP tool follows the exact same structure — a Tool definition + a handler function:
import type { Tool } from '@modelcontextprotocol/sdk/types.js'
import type { BotuyoApiClient } from '../client.js'
export const MY_TOOL: Tool = {
name: 'my_tool',
description: 'What this tool does. Include role requirements.',
inputSchema: { type: 'object', properties: { ... }, required: [...] }
}
export async function myToolHandler(
client: BotuyoApiClient, args: Record<string, unknown>
): Promise<unknown> {
return client.get(`/api/v1/mcp/...`)
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 188 lines · 38 tokens per session scan A e0ae6f06ed06
BotUyo MCP Architecture and Testing Rules is a skill published in the GitHub repository MarcoAR1/botuyo-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 1,943 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…