Tool
Is your blog directory safe to hand to an agent?
Paste the file list you already have. This runs the same path guard Stenlio runs immediately before every write, and tells you what it would decide.
Last substantive change:
Check a directory
What it is checking
Three rules, and they are the product’s own — this page calls the same functions, so its answer cannot drift away from what a real run would do.
- The path normalises to somewhere inside the repository. No leading slash, no
.., no backslashes, no percent-encoded separators. A path that fails this is refused before anything else is considered. - At least three existing articles. A directory with fewer than three
.mdor.mdxfiles cannot be registered. The conventions of a blog are learned from what is already in it, and two files are not a convention. - One extension wins. Whichever of the two is in the majority becomes the extension every future draft uses, so a mixed directory does not become more mixed.
Useful without Stenlio: these are the questions worth asking of any tool you are about to give write access to a repository. If a vendor cannot tell you which directory it may write to and what happens to a path outside it, that is the answer.
What it deliberately does not do
It does not read your repository, ask for a token, or store what you paste. It also cannot tell you whether your posts render — that depends on your framework and your frontmatter, neither of which a file list shows. What Stenlio does with the directory once registered and why the limit is an application guard rather than a GitHub permission.