Auto-Company is a software system that runs a recurring team of AI agents on a personal computer, where the agents plan work, make decisions, write code, deploy applications, and handle marketing. It is intended for autonomous product development on Windows, Linux, or macOS, using command-line agent tools and a local dashboard to track cycles and results. The catalogue entries are skills, agents, settings, and instructions that support this automated workflow.
Borrowing it
Nothing to install: this file belongs to MaxMiksa/Auto-Company. 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/MaxMiksa/Auto-Company/main/.claude/skills/community-led-growth/SKILL.mdgit clone --depth 1 https://github.com/MaxMiksa/Auto-CompanyWrote 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/maxmiksa/auto-company/community-led-growth)<a href="https://agentmods.dev/skills/maxmiksa/auto-company/community-led-growth"><img src="https://agentmods.dev/badge/skills/maxmiksa/auto-company/community-led-growth/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/maxmiksa/auto-company/community-led-growth"><img src="https://agentmods.dev/badge/skills/maxmiksa/auto-company/community-led-growth.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.00097 | $0.00392 |
| Opus 5.5 | $0.00039 | $0.00157 |
| Sonnet 5.5 | $0.00019 | $0.00078 |
| Haiku 4.5 | $0.00010 | $0.00039 |
Grade A, and why
community-led-growth 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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- community-led-growth — 100% identical, 70 lines differ
- community-led-growth — 100% identical, 0 lines differ
What it actually says
Community Led Growth
Identity
Role: Community Growth Architect
Personality: You think in networks and relationships. You understand that communities are not built, they're cultivated. You measure success not in member counts but in genuine engagement, advocacy actions, and business impact. You know when community works (authentic value exchange) and when it fails (forced engagement, corporate capture).
Expertise:
- Community platform architecture
- Ambassador program design
- User group playbooks
- Community-attributed growth
- Community health metrics
- Community content strategy
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. - For Diagnosis: Always consult
references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. - For Review: Always consult
references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
What ships with it
3 files 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.
- 1mo ago First seen · 36 lines · 97 tokens per session scan A 10355a3fabad
community-led-growth is a skill published in the GitHub repository MaxMiksa/Auto-Company (3,156 stars, last pushed 4d ago), licensed MIT. It adds 97 tokens to every session and 392 once invoked, about $0.0004 per session on Opus 5.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-30.
Other skills, from other repositories
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
hyperframes-cli
Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, timeline, history, clean, docs…
ciel
Ciel — self-improving, self-researching orchestration intelligence. A living skill graph that routes, acquires, integrates, and evolves capabilities across any skill-aware agent runtime.
design-token-architecture
CIEL's framework for three-layer design token systems (primitive→semantic→component) with CSS variables and naming conventions. Advisory only.
ui_ux_mastery
UI/UX design governance — design systems, accessibility audits, performance budgets, agentic UX patterns.
council_runner
Run Council of Five deliberations — stage orchestration, result aggregation.