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 github-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/github-skill)<a href="https://agentmods.dev/skills/zeenie-ai/opencompany/github-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/github-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/github-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/github-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Privilege Escalation · line 120 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00051 | $0.01429 |
| Opus 5.5 | $0.00020 | $0.00572 |
| Sonnet 5.5 | $0.00010 | $0.00286 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
github-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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Skill
Wrapper over the official GitHub CLI.
Typed operations for the core flows plus a custom passthrough that
covers the entire gh surface.
Tool: github
Operations
| Operation | Purpose | Key fields |
|---|---|---|
repo_clone |
Clone a repository into the workflow workspace | clone_repo (OWNER/REPO or URL), clone_dir, path |
pr_create |
Open a pull request; returns its URL | title, body, base, head, draft, fill, repo, path |
pr_list |
List pull requests (parsed JSON) | repo, state, limit |
pr_merge |
Merge a PR | pr (number/URL/branch), merge_method (squash/merge/rebase), delete_branch, repo |
issue_create |
Open an issue; returns its URL | title, body, labels, repo |
issue_list |
List issues (parsed JSON) | repo, state, limit |
custom |
Any other gh command | command — exactly what you would type after gh |
Response
{
"operation": "pr_list",
"success": true,
"url": null,
"result": [{ "number": 42, "title": "Fix login", "state": "OPEN", "url": "https://github.com/o/r/pull/42", "author": {"login": "octocat"}, "headRefName": "fix-login", "baseRefName": "main", "createdAt": "…" }],
"stdout": "…raw output…",
"stderr_tail": null
}
pr_list / issue_list return parsed JSON in result (via gh's
--json). pr_create / issue_create put the new item's URL in
url. custom commands that emit JSON (api …, … --json fields)
come back parsed in result too.
On failure the tool raises an error carrying gh's own message — surface it verbatim; gh's errors are precise (including "not logged in", which tells the user exactly how to authenticate).
Repository targeting
Inside a cloned checkout (after repo_clone, with path pointing at
it) gh infers OWNER/REPO from the git remote. Everywhere else, set the
repo field explicitly:
{ "operation": "pr_list", "repo": "octocat/hello-world", "state": "open" }
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 · 136 lines · 51 tokens per session scan A 9841a07d85e5
github-skill is a skill published in the GitHub repository zeenie-ai/OpenCompany (1,013 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 1,429 once invoked, about $0.0002 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
gh-issues
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
github
GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.
diffs
Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
browser-automation
Use when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.