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 skills/vmobifystudio/app-dev-team/house-conventionsnpx skills add vmobifystudio/app-dev-team --skill house-conventionsgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/house-conventions)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/house-conventions"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/house-conventions.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 | $0.00069 | $0.01545 |
| Opus 5 | $0.00034 | $0.00772 |
| Sonnet 5 | $0.00014 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
house-conventions 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 today.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
House conventions
The plugin ships a House Knowledge Base under knowledge/ mined from our internal shipped
apps. This skill is how an agent loads the right pack before working, so what it produces looks
like the studio's other apps — same architecture, same monetization patterns, same store hygiene.
When to use
Invoke this before the first edit/spec on any ticket, sprint, or asset. It costs one read and prevents a whole class of "this doesn't match how we build" rework.
Procedure
-
Identify what you're about to do and load the matching pack(s). The packs live at
${CLAUDE_PLUGIN_ROOT}/knowledge/<pack>.md. IfCLAUDE_PLUGIN_ROOTis not set in your environment, glob for**/knowledge/stack-defaults.mdinside the plugin install and read the packs from that directory. If you genuinely cannot locate the packs, STOP and report a blocker — do not silently proceed on generic defaults; that is exactly the failure this skill exists to prevent.You are about to… Read Pick stack / versions / libraries stack-defaults.mdWrite or review iOS code ios-conventions.md(+stack-defaults.md)Write or review Android code android-conventions.md(+stack-defaults.md)Add ads, IAP, or a paywall monetization.mdAdd analytics / events / KPIs analytics.mdPrepare store assets / submission aso.mdSet up git, CI, signing, releases git-workflow.mdWrite a vision, PRD, or backlog No pack — the shape lives in prd-builder/requirements-intake, not here. Readstack-defaults.mdonly where the document names a platform, version or library; otherwise this skill has nothing for you and you are done in one line. -
Treat the pack as the floor. Follow it unless the project's own
docs/(architecture, engineering principles,CLAUDE.md) explicitly overrides a specific rule — a project may be stricter, never sloppier.Tier: default to the Flagship rules in each pack. If the project declares itself a utility app (in its
docs/orCLAUDE.md), apply the Utility branch where a pack defines one (e.g. ad-first monetization, leaner stack) — seeknowledge/README.md§Tiers.
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.
- today First seen · 92 lines · 69 tokens per session scan A 18481daa07db
house-conventions is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 69 tokens to every session and 1,545 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
archon
Autonomous multi-session campaign agent. Decomposes large work into phases, delegates to sub-agents, reviews output, and maintains campaign state across context windows. Use for work that spans multiple sessions and needs persistent state, quality judgment, and strategic decomposition.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
prd
Generates a Product Requirements Document from a natural language app description. Asks clarifying questions, researches similar apps, defines scope, stack, architecture, and produces a structured PRD that Archon can decompose into a campaign.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.
migrate
Scan the project and migrate existing documentation into OKF format. Use when the user wants to populate the knowledge base from existing docs, README, schemas, API specs, runbooks, or any structured project knowledge. Trigger on "migrate to okf", "populate the knowledge base", "scan my docs", "convert docs to okf"…
init
Initialize OKF knowledge base files in the current project. Use when the user wants to start documenting their project for claude-mega-brain, or when the user says "init mega brain", "setup the knowledge base", "cria o okf", "inicializa o mega brain", "quero usar o mega brain", "criar a estrutura do knowledge base"…