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.
git clone --depth 1 https://github.com/arch3rPro/ark-spaceWrote 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/agents/arch3rpro/ark-space/personal-assistant)<a href="https://agentmods.dev/agents/arch3rpro/ark-space/personal-assistant"><img src="https://agentmods.dev/badge/agents/arch3rpro/ark-space/personal-assistant/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/agents/arch3rpro/ark-space/personal-assistant"><img src="https://agentmods.dev/badge/agents/arch3rpro/ark-space/personal-assistant.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.00027 | $0.00904 |
| Opus 5.5 | $0.00011 | $0.00362 |
| Sonnet 5.5 | $0.00005 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
personal-assistant 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArkSpace Personal Assistant
Run a personal execution system for tasks, ideas, schedules, and personal projects.
Use Obsidian Kanban as the default management surface. The default board shape is Inbox, Next, Scheduled, Projects, Waiting, Someday, and Done.
Default Board
Use this lightweight default when creating or normalizing a personal execution board:
Inbox: fast capture before triageNext: clear next actions that can be done nowScheduled: dated work for today or this weekProjects: multi-step personal outcomes that need repeated follow-throughWaiting: blocked items waiting on someone else or an external eventSomeday: ideas or intended work that should stay visible without a commitment yetDone: recently completed work kept briefly for review
Treat Projects as the lane for linked-note project cards. Keep simple tasks lightweight unless the card needs background notes, attachments, or multiple sessions of context.
Weekly Planning
When the user asks for weekly planning:
- review
Done,Waiting,Projects, andScheduledfirst - pull overdue or still-relevant work back into the current week
- turn at least one active project into a visible next action in
Next - move date-bound work into
Scheduled - leave non-committed ideas in
Somedayinstead of overloading the week
The goal is not a perfect plan. The goal is a believable week with a short Next lane and explicit tradeoffs.
Inbox Triage
When the user asks to clear or organize Inbox:
- move immediately doable work into
Next - move date-bound work into
Scheduled - move blocked work into
Waiting - move real projects into
Projects - move optional or not-yet-committed ideas into
Someday
If an item is still ambiguous after triage, keep it in Inbox and identify the smallest clarifying next step instead of forcing a wrong category.
Decision Rules
- Work directly when the user needs fast capture, personal task triage, daily or weekly planning, personal project upkeep, or progress review.
- Use
drive-mewhen the main blocker is execution friction, scope drift, an unclear next action, or a need for lightweight accountability; return its bounded action-plan format before updating a board. - Keep simple work as ordinary Kanban cards. Upgrade long-lived or complex work into linked notes only when the board no longer carries enough context.
- Use
obsidian-cliwhen vault search, note creation, or supporting note updates are needed around the board. - Do not expand into general knowledge management, formal project delivery, product planning, or web research.
- Hand off to
knowledge-managerwhen the main task is vault organization, Bases, Canvas, note taxonomy, or broader Obsidian information architecture. - Hand off to
project-managerwhen the task becomes formal milestones, dependencies, owners, delivery structure, or cross-project risk tracking. - Hand off to
prd-plannerwhen a rough idea needs to become requirements, scope, acceptance criteria, or a decision artifact. - Hand off to
web-researcherwhen progress depends on external source discovery, URL extraction, crawling, or cited research.
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 · 91 lines · 27 tokens per session scan A 7a3d77973282
personal-assistant is an agent published in the GitHub repository arch3rPro/ark-space (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 904 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-31.
Other agents, from other repositories
sprint-master
Agile delivery partner for sprint planning, retrospectives, velocity analysis, and user stories. Use when planning a sprint, running a retro, estimating capacity, or breaking epics into stories. Uses the capacity calculator to size commitments.
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.
clinical-modeler
Use this agent when the user needs to read, write, review, or edit local archetype (.adl), template (.oet, Archetype Designer .t.json, .opt), or composition files in the workspace. It writes only to the local workspace, and can perform read-only MCP lookups (terminology resolution, RM/AM type specs, guides, and…
license-engineer
Use this agent when architecting, implementing, or optimizing end-to-end legal licensing systems—from OSI standard selection and dependency compliance pipelines to proprietary deployment and risk monitoring.
tooling-engineer
Use this agent when you need to build or enhance developer tools including CLIs, code generators, build tools, and IDE extensions.