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 Bevel-Software/Hexis --skill productivity-startgit clone --depth 1 https://github.com/Bevel-Software/HexisWrote 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/bevel-software/hexis/productivity-start)<a href="https://agentmods.dev/skills/bevel-software/hexis/productivity-start"><img src="https://agentmods.dev/badge/skills/bevel-software/hexis/productivity-start/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/bevel-software/hexis/productivity-start"><img src="https://agentmods.dev/badge/skills/bevel-software/hexis/productivity-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00058 | $0.01305 |
| Opus 5.5 | $0.00023 | $0.00522 |
| Sonnet 5.5 | $0.00012 | $0.00261 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade A, and why
productivity-start 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 6d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start
Names like
~~chator~~project trackermean whichever tool of that kind is connected: a tool in one of your Hexis plugins, or one your agent has itself. The knowledge base is this workspace's knowledge base in Hexis, plus any other docs tool that is connected. When a source is not connected, skip it and say what you could not check.
Initialize the task and memory systems (see the task-management and memory-management skills).
Instructions
1. Check What Exists
Check the agent's working directory for:
TASKS.md- task listCLAUDE.md(or your agent's equivalent) - working memory
And search the knowledge base for:
- A
Glossarypage People/andProjects/folders- A
How we workpage
2. Create What's Missing
If TASKS.md doesn't exist: Create it with the standard template (see task-management skill). Place it in the agent's working directory.
If CLAUDE.md doesn't exist: This is a fresh setup - begin the memory bootstrap workflow (see below).
Do not create empty knowledge base pages. The knowledge base is shared: a page appears when there is something true to put in it, with the person's go-ahead.
3. Orient the User
If everything was already initialized:
Your tasks and memory are both loaded.
- Ask for productivity-update to sync tasks and check memory
- Ask for a comprehensive update for a deep scan of all activity
If memory hasn't been bootstrapped yet, continue to step 4.
4. Bootstrap Memory (First Run Only)
Only do this if CLAUDE.md doesn't exist yet.
Start with what the team already wrote down: read the knowledge base's Glossary, How we work and About us pages if they exist. Do not ask about anything they already answer.
The best source of workplace language is the user's actual task list. Real tasks = real shorthand.
Ask the user:
Where do you keep your todos or task list? This could be:
- A local file (e.g., TASKS.md, todo.txt)
- An app (e.g. Asana, Linear, Jira, Notion, Todoist)
- A notes file
I'll use your tasks to learn your workplace shorthand.
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.
- 6d ago First seen · 164 lines · 58 tokens per session scan A 36720d2b361b
productivity-start is a skill published in the GitHub repository Bevel-Software/Hexis (115 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,305 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-10-10.
Other skills, from other repositories
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
rem-page-org
What an organisation's page in the notebook is made of — the fixed sections, when a company earns a page at all instead of staying a field on a person's, and the rules that keep it from becoming a second copy of everyone who works there. Composed into every stage that writes one.
rem-project-sessions
Write or update one project page from the owner's messages and a bounded packet of local project evidence.
pod-resume
Reconstruct context for a returning developer. Reads .cocoplus/ state and generates a narrative summary of project status, last achievements, pending tasks, recent decisions, available patterns, CocoCupper insights, and recommended next action.
kb-workflow
Use before starting any non-trivial task to search the knowledge base for context, and after completing work to capture findings. Teaches the token-efficient retrieval pattern and self-learning loop.