OpenCompany is an application for creating AI employees that work on assigned jobs in the background on the user's computer, using teams of specialized agents coordinated by a lead agent. People connect these employees to tools such as email, calendars, messages, and code, then define their workflows through a visual editor.
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 zeenie-ai/OpenCompany --skill memory-skillgit clone --depth 1 https://github.com/zeenie-ai/OpenCompanyWrote 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/zeenie-ai/opencompany/memory-skill)<a href="https://agentmods.dev/skills/zeenie-ai/opencompany/memory-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/memory-skill/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/zeenie-ai/opencompany/memory-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/memory-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 4 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- high Memory Poisoning · line 36 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- high Memory Poisoning · line 36 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- high Memory Poisoning · line 93 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00032 | $0.00874 |
| Opus 5.5 | $0.00013 | $0.00350 |
| Sonnet 5.5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
memory-skill 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Management Skill
This skill enables you to manage conversation memory using the SimpleMemory node's markdown-based storage system.
Memory Architecture
Short-Term Memory (Markdown)
- Visible and editable in the SimpleMemory node's UI
- Stored as markdown with timestamped entries
- Window-based: keeps last N message pairs (configurable)
- Format:
### **Human** (timestamp)and### **Assistant** (timestamp)
Long-Term Memory (Vector DB)
- Automatically archives messages that exceed the window
- Semantic search for relevant past conversations
- Enabled via
longTermEnabledin SimpleMemory node
Capabilities
- View History: See recent conversation in markdown format
- Save Notes: Add explicit notes/memories to the conversation
- Search Memory: Find relevant past conversations semantically
- Clear Memory: Reset conversation history
When to Use
Save information when:
- User says "remember this" or "don't forget"
- Important context is shared for future use
- User wants to note something specific
Recall information when:
- User asks "do you remember..."
- Context from earlier is needed
- User references previous discussions
View history when:
- User wants to see conversation log
- Debugging or reviewing past exchanges
Tool Reference
memory-save
Add a note or memory entry to the conversation history.
Parameters:
content(required): Information to rememberrole(optional): "note" (default) or "context"
Example:
{
"content": "User's favorite color is blue",
"role": "note"
}
memory-get
Get recent conversation history or search for specific content.
Parameters:
count(optional): Number of recent messages (default: 10)search(optional): Search term to find specific memories
Example - Recent history:
{
"count": 5
}
Example - Search:
{
"search": "favorite color"
}
memory-clear
Clear conversation history.
Parameters:
confirm(required): Must be true to clear
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 · 158 lines · 32 tokens per session scan A 0858671857ad
memory-skill is a skill published in the GitHub repository zeenie-ai/OpenCompany (1,037 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 874 once invoked, about $0.0001 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
knowledge-unlinked-claims
Review remembered Knowledge claims still unlinked after deterministic relinking. Assign subject pages, create pages for substantial missing subjects, retire exact duplicates and explicitly replaced claims, and fold durable outcomes into page State. Use for unlinked-claim cleanup or the scheduled review that follows…
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn). Routes meetings to knowledge-meeting-ingest and short thoughts…
knowledge-meeting-ingest
Ingest meeting transcripts from any recorder into Knowledge with attendee enrichment, timeline merge, supported decisions and commitments, and verification of substance and sequence. Summary-only input is not a verified meeting ingestion.
knowledge-correct
Correct or withdraw specific saved Knowledge claims, explicit relationships, or pages at the user's request, preserving provenance and inspecting affected knowledge. Use for “that's wrong”, “retract that”, or a Knowledge chat reference; not automatic contradiction resolution or physical erasure.
knowledge-source-ingest
Incrementally ingest enumerable external sources into Knowledge with canonical source identity, retained snapshot manifests, overlap-aware diffing, and reconciliation of changed or deleted items. Includes a generic manifest tool and a read-only Discrawl adapter.
knowledge-automation
Create scheduled Knowledge ingestion automations with a verified worker, private-vault authority, and an end-to-end scheduled run. Use when asked to schedule or repair recurring ingestion from any source.