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 Aicoo-Team/AICOO-Skills --skill invite-teamgit clone --depth 1 https://github.com/Aicoo-Team/AICOO-SkillsWrote 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/aicoo-team/aicoo-skills/invite-team)<a href="https://agentmods.dev/skills/aicoo-team/aicoo-skills/invite-team"><img src="https://agentmods.dev/badge/skills/aicoo-team/aicoo-skills/invite-team/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/aicoo-team/aicoo-skills/invite-team"><img src="https://agentmods.dev/badge/skills/aicoo-team/aicoo-skills/invite-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
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 →
- medium MCP Rug Pull · line 42 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Data Exfiltration · line 76 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 85 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00088 | $0.01297 |
| Opus 5.5 | $0.00035 | $0.00519 |
| Sonnet 5.5 | $0.00018 | $0.00259 |
| Haiku 4.5 | $0.00009 | $0.00130 |
Grade A, and why
invite-team scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://www.aicoo.io/api/v1/identity" \ How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invite Team — Two Ways To Bring People In
Offer both and let the user pick per person:
- Copy-paste onboarding prompt — best for technical teammates. A block they paste into their own Claude Code / Codex / agent runtime that installs the skills, signs them in, builds their memory, and connects them back. Works for anyone, needs no Team plan.
- Invite link — best for anyone with (or willing to make) an Aicoo account.
Adds them to your Team plan's seats. Requires you to own/admin a Team plan and
the
os.team:writescope.
Requires being signed in (onboarding skill). Resolve the token with the
pack's scripts/aicoo-auth.sh:
export AICOO_API_KEY="$(bash /path/to/aicoo-skills/scripts/aicoo-auth.sh)".
A) Copy-paste onboarding prompt (always available)
Get the inviter's username, then hand the user a ready-to-share block.
curl -s "https://www.aicoo.io/api/v1/identity" \
-H "Authorization: Bearer $AICOO_API_KEY" | jq -r '.identity.username // .profile.username'
Present exactly this (substitute <username>; if you also made an invite link
in section B, add it as an optional line):
Send this to your teammate — they paste it into their AI agent (Claude Code, Codex, …):
---
Set me up on Aicoo and connect me to my teammate.
1. Install the Aicoo skills:
npx skills add Aicoo-Team/AICOO-Skills
(or: git clone https://github.com/Aicoo-Team/AICOO-Skills.git ~/.claude/plugins/aicoo-skills)
2. Sign in with Aicoo:
node ~/.claude/plugins/aicoo-skills/scripts/aicoo-login.mjs
3. Run the Aicoo onboarding skill to build my agent memory and share my agent.
4. Connect me to @<username> on Aicoo (accept their team invite if I have one).
---
The teammate's agent does the install → sign-in → onboarding → connect end to end. Nothing else needed from you.
B) Invite link (Team plan)
B1. Check team status first
curl -s "https://www.aicoo.io/api/v1/os/team" \
-H "Authorization: Bearer $AICOO_API_KEY" \
| jq '{hasTeam, role, canInvite, seatsAvailable: .team.seatsAvailable, members: (.members|length), pendingInvites}'
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.
- 2mo ago First seen · 117 lines · 88 tokens per session scan A 329ed48e429f
invite-team is a skill published in the GitHub repository Aicoo-Team/AICOO-Skills (35 stars, last pushed 3mo ago), licensed MIT. It adds 88 tokens to every session and 1,297 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
feature-request
Gathers a bug report, feature request or feedback in conversation and routes it to the in-app Report a Problem dialog, the public issue forms, or SECURITY.md for a vulnerability (never a public issue); load when the user wants to report a problem, send feedback or suggest an improvement.
goal-loop
Bootstrap a goal-driven self-improving AutoNudge loop from a goal plus an anchor directory, then run the board autonomously until the Definition of Done is met.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…