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 skills add nocodework/ai-context-kit --skill company-contextgit clone --depth 1 https://github.com/nocodework/ai-context-kitWrote 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/nocodework/ai-context-kit/company-context)<a href="https://agentmods.dev/skills/nocodework/ai-context-kit/company-context"><img src="https://agentmods.dev/badge/skills/nocodework/ai-context-kit/company-context.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.00101 | $0.01193 |
| Opus 5 | $0.00051 | $0.00596 |
| Sonnet 5 | $0.00020 | $0.00239 |
| Haiku 4.5 | $0.00010 | $0.00119 |
Grade A, and why
company-context 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 7d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
company-context — build a reusable company context file
Interview the user about their company and write a clean company-context.md they can feed into any AI tool so it answers clients, writes content and proposals in the company's voice, and stops guessing the business.
If company-context.md already exists in the current directory, read it first, give the user a two-line summary, and ask what has changed — then update those parts and refresh the Last updated line. Don't re-run the interview from scratch and don't overwrite their file without confirmation.
How to run the interview
- Ask in small batches (3–5 at a time), conversational, not a giant form.
- Interview and write the file in the user's language — if they write in Polish, ask and write in Polish.
- Pre-fill from anything you can see (their site if they share it, the repo, earlier messages) and ask them to confirm rather than re-asking.
- Sections 1–3 (the company, offer, customers) are the core — cover them first, then offer the rest; a file with just the core is already useful, so let the user stop there if they want.
- On "I don't know": give one concrete example answer; if they still don't know, skip the point and move on — don't push.
- After the core questions, proactively flag gaps: name 2–4 specific things that are missing and would make the context more useful (e.g. "you haven't described your ideal customer's main pain — want to add it?").
- If they have several distinct services or audiences, capture each briefly rather than blending them.
- When done, write the file (see Output) in their own wording and tone.
What to cover
- The company — name, a one-line description of what it does, website, stage/size.
- Offer — products/services, who each is for, pricing model (optional), and what genuinely makes it different (the real differentiators, not slogans).
- Customers — the ideal customer (industry, size, role), the problem you solve, the outcome you deliver, and 2–3 real (or anonymised) client examples.
- Personas — the key people involved: who decides to buy, who actually uses it, and each one's main goals and pains.
- Positioning & messaging — the category you compete in, your value proposition in a sentence, proof/credibility, and competitors you're often compared to.
- Voice — tone, words and phrases to use, and ones to avoid; any brand or style rules.
- Team — key people and who does what (optional).
- Client-facing know-how — the questions clients ask most often (with your answers), common objections and how you handle them, and your typical process from first contact to delivery.
- Anything else — an open prompt for what any AI should know to represent the company well.
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.
- 7d ago First seen · 56 lines · 101 tokens per session scan A 832e232700dd
company-context is a skill published in the GitHub repository nocodework/ai-context-kit (24 stars, last pushed 2mo ago), licensed MIT. It adds 101 tokens to every session and 1,193 once invoked, about $0.0005 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-30.
Other skills, from other repositories
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.
prompt-architect
Analyzes and improves prompts using 31 frameworks across 7 intent categories. Use when a user wants to improve, rewrite, structure, or engineer a prompt — including requests like "help me write a better prompt", "improve this prompt", "what framework should I use", "make this prompt more effective", or any prompt…
tidy
A simple example skill for cleaning up a project.
extremerouter-web-search
Web search via ExtremeRouter /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / Linkup / SearchAPI / You.com / Perplexity. Use when the user wants to search the web, look up information, find articles, or query a search engine.
extremerouter
Entry point for ExtremeRouter — local/remote AI gateway with OpenAI-compatible REST for chat, image, TTS, embeddings, web search, web fetch. Use when the user mentions ExtremeRouter, NINEROUTERURL, or wants AI without writing provider boilerplate. This skill covers setup + indexes capability skills; fetch the relevant…
gog-workspace
Use the gog CLI for Google Workspace tasks across Gmail, Calendar, Drive, Docs, Sheets, Contacts, and related services. Use when the user asks to check email, search Gmail, inspect calendar events, find Drive files, read Docs or Sheets, or manage Google Workspace data through gog.