agentleFS
Sign inStart free
wernerbattwernerbatt/obsidian-gtd-cli/AGENTS.md

obsidian-gtd-cli

AGENTS.md0 starsChanged 7 months agoMITView on GitHub

Agent instructions and skill discovery for the Obsidian GTD CLI toolkit.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository9 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If your agent expects a different skills path, mirror or symlink those folders (for example, .codex/skills/).

    line 16
  2. Very specific:

    Always follow the instructions inside each SKILL.md when using a skill.

    line 17
  3. Very specific:

    All vault operations go through the Obsidian CLI — see the /obsidian skill.

    line 21
  4. Distinctive:

    Never use direct file I/O for vault files — always go through the Obsidian CLI.

    line 24
  5. Distinctive:

    Do not modify tasks or vault files without explicit user confirmation.

    line 28
  6. Distinctive:

    If a tool supports preview or dry-run behavior, use it when asked and summarize changes before applying them.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS

Purpose

This repository provides a Python CLI toolkit plus reusable skills for AI agents that can read AGENTS.md and SKILL.md files.

Skills

  • Primary skills live in .claude/skills/*/SKILL.md.
  • Available skills: clarify, organize, project, purge, review, stuck, systems-review, obsidian, reflect, task-prioritisation, next.
  • If your agent expects a different skills path, mirror or symlink those folders (for example, .codex/skills/).
  • Always follow the instructions inside each SKILL.md when using a skill.

Tooling

  • All vault operations go through the Obsidian CLI — see the /obsidian skill.
  • tools/obsidian_cli.py is a thin Python wrapper around the CLI binary (used when Python is more convenient than shell).
  • Configuration lives in config.yaml (notably obsidian_bin, vault_name, and GTD paths).
  • Never use direct file I/O for vault files — always go through the Obsidian CLI.

Safety and Confirmation

  • Do not modify tasks or vault files without explicit user confirmation.
  • If a tool supports preview or dry-run behavior, use it when asked and summarize changes before applying them.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free