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 agentmods add instructions/ronnycoding/my-personal-assistant/gemini-mdgit clone --depth 1 https://github.com/ronnycoding/my-personal-assistantWrote 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/instructions/ronnycoding/my-personal-assistant/gemini-md)<a href="https://agentmods.dev/instructions/ronnycoding/my-personal-assistant/gemini-md"><img src="https://agentmods.dev/badge/instructions/ronnycoding/my-personal-assistant/gemini-md.svg" alt="Measured on agentmods" 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 | $0.00469 | $0.00469 |
| Opus 5 | $0.00234 | $0.00234 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
my-personal-assistant GEMINI.md 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 2d 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEMINI.md
Directory Overview
This directory contains a collection of personal AI agents and scripts designed to automate tasks on macOS using AppleScript. The project is built around the concept of "commands," which are defined in TOML files in the .gemini/commands directory. These commands orchestrate the execution of AppleScript files located in the .claude/skills directory.
The project is well-documented and includes a testing framework for ensuring the reliability of the scripts.
Key Files
README.md: The main entry point for understanding the project. It provides a high-level overview, setup instructions, and usage examples.PROJECT_SUMMARY.md: A detailed summary of the project's status, completed work, and future roadmap..gemini/commands/: This directory contains the command definitions in TOML format. Each file defines a command, its associated prompt, and the script it executes..claude/skills/: This directory contains the individual AppleScript files, organized by application (e.g.,apple-mail,calendar,reminders).tests/: This directory contains the testing framework for the AppleScript scripts, including test runners, assertions, and test data generators.docs/: This directory contains detailed documentation about the project, including the command API, permissions setup, and development conventions.
Usage
To use this project, you will need to have a macOS environment with the necessary applications (Mail, Calendar, Reminders) and permissions configured. The README.md file provides detailed instructions on how to set up the project and run the agents.
Once the project is set up, you can interact with the agents by providing natural language commands. The agent will then select and execute the appropriate command to fulfill your request.
Development
This project is under active development. To contribute, you can create new commands, improve existing scripts, or enhance the testing framework. The docs/SKILLS_API.md file provides a comprehensive guide to creating and registering new commands.
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.
- 2d ago First seen · 28 lines · 469 tokens per session scan A 3ba675e70f71
my-personal-assistant GEMINI.md is an instructions file published in the GitHub repository ronnycoding/my-personal-assistant (12 stars, last pushed 9mo ago), licensed MIT. It adds 469 tokens to every session, about $0.0023 per session on Opus 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-09-02.
Other instructions, from other repositories
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
tmetric-minimal-mcp CLAUDE.md
Claude Code instructions for guglielmo/tmetric-minimal-mcp, covering claude.md, development commands, project architecture, file structure and core architecture patterns.
shelly-forge CLAUDE.md
Claude Code instructions for mslavov/shelly-forge, covering documentation usage guidelines, critical: framework-first reading order, 📚 mandatory reading order, pre-task protocol and post-task protocol.
vibelive AGENTS.md
AGENTS.md instructions for pooriaarab/vibelive, covering agents.md, repository context, pull requests, cloud agents (cursor) and install & test.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).