markdowndb
Turn markdown files into structured, queryable data with JS. Build markdown-powered docs, blogs, and sites quickly and reliably.
Runs with mockssource: GitHubhomepageTypeScriptMITcommit f53cfef49ffc
TypeScript, MIT licensed. The project labels itself: awesomeness, catalog, contentlayer, contentlayer nextjs, contentlayer typescript, database, headless cms and jamstack.
markdowndb runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
After npm install and build, the CLI indexes markdown into a real SQLite database (13 files read back from markdown.db), the test suite passes 13 suites and 86 tests, and the MySQL backend indexes 3 files with tag and tag-filter queries answered by a local schema-correct mock.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Published registry tarball [email protected] contains a stale 35-line CLI: npx mddb ./one ./two fails with 'Error loading configuration file' and no --exec/--help support20 minutes
- MySQL backend needs optional peer mysql2, not auto-installed5 minutes
- Config include/exclude globs are matched against absolute walk paths, so relative patterns like c1/** matched nothing5 minutes
- Node 18.19.1 is below engines >=20; npm install printed EBADENGINE warning2 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 75 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm test exited 0 with '13 passed, 13 total' suites and '86 passed, 86 total' tests; node dist/src/bin/index.js /work/repo/__mocks__/content exited 0 and created markdown.db with 13 files read back via bundled sqlite3; sh run-mysql-test.sh printed MYSQL_MOCK_INDEXED_FILES: 3 CLIENT_EXIT=0 and sh mysql-e2e.sh printed GETFILES 3 BY_TAG 1 E2E_EXIT=0
- Model tokens used
- 14,587,857
- Exact commit tested
- f53cfef49ffc
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `npm test` → exit 0, `Test Suites: 13 passed, 13 total; Tests: 86 passed, 86 total`. - CLI `node dist/src/bin/index.js /work/repo/__mocks__/content` → exit 0, created `markdown.db`, re… - MySQL backend against my wire-protocol mock → `MYSQL_MOCK_INDEXED_FILES: 3`, `CLIENT_EXIT=0`; `GE… - `git status --short` clean; install/build succeeded (Node 18 warning only). tokens used 14,587,857 All final checks pass and the repo is clean. Final report: **Verification performed** - `npm test` → exit 0, `Test Suites: 13 passed, 13 total; Tests: 86 passed, 86 total`. - CLI `node dist/src/bin/index.js /work/repo/__mocks__/content` → exit 0, created `markdown.db`, re… - MySQL backend against my wire-protocol mock → `MYSQL_MOCK_INDEXED_FILES: 3`, `CLIENT_EXIT=0`; `GE… - `git status --short` clean; install/build succeeded (Node 18 warning only).
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 15 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 2.91 |
Topics (from GitHub)
awesomenesscatalogcontentlayercontentlayer-nextjscontentlayer-typescriptdatabaseheadless-cmsjamstackmarkdown
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/markdowndb)Questions
- Does markdowndb run?
- markdowndb runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test markdowndb?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f53cfef49ffc. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test markdowndb?
- The run that produced this verdict cost $2.91: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does markdowndb take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does markdowndb need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing markdowndb?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for markdowndb?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.