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 codesstar/loci --skill skillgit clone --depth 1 https://github.com/codesstar/lociWrote 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/codesstar/loci/skill)<a href="https://agentmods.dev/skills/codesstar/loci/skill"><img src="https://agentmods.dev/badge/skills/codesstar/loci/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/codesstar/loci/skill"><img src="https://agentmods.dev/badge/skills/codesstar/loci/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 Rogue Agent · line 34 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 34 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00178 |
| Opus 5.5 | $0.00008 | $0.00071 |
| Sonnet 5.5 | $0.00004 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
loci 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 8d 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.
What it actually says
Loci entry adapter
Read the existing brain path from ~/.loci/brain-path, verify it, then read its LOCI.md. Resolve <brain-path> to that actual directory. Follow its startup preference reader and first-use trigger for LOCI-RULES.md; do not maintain another copy of the operation rules here.
If the user asks to install Loci and no brain exists, follow the official docs/AI-INSTALL.md from https://github.com/codesstar/loci. Use its Node installer, preserve existing data, and verify access with the current client. Do not initialize personal files by hand or assume that installing this skill connects a client without local tools.
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.
- 8d ago Changed · -99 lines 2c79c616a76d
- 1mo ago First seen · 111 lines · 21 tokens per session scan A be160bdabbfa
loci is a skill published in the GitHub repository codesstar/loci (508 stars, last pushed 9d ago), licensed MIT. It adds 21 tokens to every session and 178 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
collaboration-intelligence
Maintain and use a cross-channel collaboration map of rooms, people, agents, agent owners, relationships, expertise, ownership, roster, priority/VIP handling, and recent context. Trigger when a task or message carries room/channel/sender/member metadata; the user asks who is in a room, what it is for, who owns or…
context-drop
Tiny Swift CLI that reads the focused app's text selection via the macOS Accessibility API. Sutando.app's "drop context" action (hotkey configurable via state/hotkeys.json) shells out to this binary to capture what you have highlighted.
import-claude-context
Bring the owner's Claude Code history into Sutando: index, extract and haiku-summarise the stock /.claude/projects transcripts, stage the result, show the owner a digest and — only on their 'bring it in' — land it in core memory, notes/claude-import/ and People payloads. Triggers: 'import my Claude history', 'read my…
context-reconstruct
Re-anchor on the durable record (current-track, live owner thread, pending-questions, relay, buildlog) before acting on anything that depends on earlier context. Read, do not recall.
learning-window
Persist collection evidence and plan unread room windows separately from learned facts.
session-recap
Reconstruct what happened in a past core session — from a high-level summary down to verbatim owner quotes — by reading the raw session transcripts (complete, crash-proof, unbiased), not the curated relay/handoff notes.