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 aAAaqwq/AGI-Super-Team --skill company-wikigit clone --depth 1 https://github.com/aAAaqwq/AGI-Super-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/aaaaqwq/agi-super-team/company-wiki)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/company-wiki"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/company-wiki/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/aaaaqwq/agi-super-team/company-wiki"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/company-wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.00623 |
| Opus 5 | $0.00010 | $0.00311 |
| Sonnet 5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
company-wiki 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Company Wiki
Structured knowledge base about WeLabelData company: domains, hosting, services, accounts, infrastructure, architecture decisions. Single source of truth.
When to use
- "запиши в базу знань" / "save to company wiki"
- "які домени в нас є?" / "what domains do we have?"
- "де хоститься сайт?" / "where is the site hosted?"
- "які сервіси ми використовуємо?" / "what services do we use?"
- Looking up infrastructure details (DNS, hosting, payments, etc.)
- Recording new company assets (domains, accounts, services)
Paths
| What | Path |
|---|---|
| Wiki root | ~/company-wiki/ |
| Domains & DNS | ~/company-wiki/domains.md |
| Services & accounts | ~/company-wiki/services.md |
| Infrastructure | ~/company-wiki/infrastructure.md |
| Products | ~/company-wiki/products.md |
| Architecture decisions | ~/company-wiki/decisions.md |
How to execute
Read information
# Find specific info
grep -ri "KEYWORD" ~/company-wiki/
# Read a specific section
cat ~/company-wiki/domains.md
Write information
- Identify the correct file based on the type of information
- Read current file content
- Add or update the relevant section
- Keep format consistent: use markdown tables and headers
File structure conventions
Each file follows this pattern:
# [Topic]
## [Category]
| Field | Value |
|-------|-------|
| Name | ... |
| ... | ... |
### Notes
- Additional context
Examples
Example 1: Record a new domain
# Read current domains
cat ~/company-wiki/domains.md
# Edit to add new domain entry
Example 2: Look up hosting details
grep -i "hosting\|cloudflare\|gcs" ~/company-wiki/infrastructure.md
Example 3: Record architecture decision
Add to ~/company-wiki/decisions.md:
## YYYY-MM-DD: [Decision Title]
- **Context:** Why this came up
- **Decision:** What was decided
- **Alternatives considered:** What else was considered
- **Status:** Active / Superseded by [X]
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 · 104 lines · 21 tokens per session scan A 079d0fab0e77
company-wiki is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (92 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 623 once invoked, about $0.0001 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-05.
Other skills, from other repositories
a2wave-memory
Progressively recall and maintain a2wave cross-session memory through a compact startup catalog, bounded topics, and searchable history.
optimize-learnings
Audit and curate the learnings memory namespace — the one namespace nothing re-derives, so the only one that rots. Runs moflo's mechanical audit to nominate stale, unused, and near-duplicate entries, then decides entry by entry whether to keep, retire, compress, or merge, and propagates the result to the shared…
meditate
Deliberate session retrospective — look back over what you just did, distill the durable, reusable lessons (not session trivia), and write them to the learnings memory namespace, deduped against what is already stored. Use at the END of a meaningful chunk of work to capture high-signal lessons worth keeping long-term.…
memory-team
Guided setup for sharing moflo's durable learnings through a git-tracked JSONL artifact — for a whole TEAM on one repo, OR for one person across several MACHINES (a team of one). Use when the user says "share learnings with my team", "commit our moflo memory", "sync memory across my laptop and desktop", "set up…
memory-patterns
Persistent memory patterns for moflo agents — session memory, long-term knowledge, pattern learning, and cross-session context via moflo's node:sqlite + HNSW vector store. Use when building stateful agents or assistants that need to remember across runs.
memory-worktree
Verify, customize, or opt out of moflo's AUTOMATIC durable-learning sharing across git worktrees / Conductor workspaces on one machine. As of the worktree-auto-sharing change this is on by default — learnings converge across a repo's worktrees with no setup. Use when the user asks "is memory shared across my…