Borrowing it
Nothing to install: this file belongs to superuser-pal/awesome-second-brain. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/superuser-pal/awesome-second-brain/main/.claude/commands/core/ingest-url.mdgit clone --depth 1 https://github.com/superuser-pal/awesome-second-brainWrote 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/commands/superuser-pal/awesome-second-brain/ingest-url)<a href="https://agentmods.dev/commands/superuser-pal/awesome-second-brain/ingest-url"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/ingest-url.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.1 | $0.00039 | $0.00650 |
| Opus 5 | $0.00019 | $0.00325 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
ingest-url 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 7d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest URL
Extract a web page as clean markdown and route it directly to the vault in one step.
Usage
/ingest-url <url>
Workflow
1. Preflight Check
Verify defuddle CLI is installed:
defuddle --version
If not installed, fail gracefully:
⚠️ defuddle CLI not found.
Install it with:
npm install -g defuddle-cli
Then re-run: /ingest-url <url>
Stop here — do not continue without defuddle.
2. Extract Content with Defuddle
defuddle parse <url> --md
Capture the markdown output. If defuddle returns an error or empty output:
⚠️ defuddle could not extract content from <url>.
Try opening the URL in a browser to confirm it's accessible.
Stop here if extraction fails.
3. Stage as Raw Note
Save the extracted markdown to inbox/raw/ using the standard InboxRaw schema:
---
date: YYYY-MM-DD
created: YYYY-MM-DD
status: unprocessed
---
# [Page title from defuddle output]
> Source: <url>
[Extracted markdown content]
Filename: [slugified-title]-[YYYY-MM-DD].md
4. Process
Run /process on the staged note to:
- Assign
domainfrom content analysis - Assign
type(expectsourcefor most URL ingests, but allow content analysis to override) - Complete frontmatter (
name,description,tags,origin: url) - Move from
inbox/raw/→inbox/ready/
5. Distribute
Run /distribute on the processed note to:
- Route to
domains/[domain]/02_PAGES/(or02_PAGES/sources/if thesources/sub-folder exists) - Apply steps 3b and 3c from the distribute workflow (type assignment + sub-folder routing)
- Present routing plan and wait for confirmation
6. Report
✓ Ingested: <url>
Extracted: [Page title]
Domain: [domain]
Type: source
Destination: domains/[domain]/02_PAGES/[sub-folder/][filename]
Notes
- This command chains three existing operations — no new logic beyond the chain itself.
/processand/distributeretain their normal confirmation prompts; this command does not bypass them.- If the URL content is clearly not a
source(e.g., a decision log or report),/processmay assign a different type — that is correct behavior. - See [[.claude/skills/defuddle/SKILL|defuddle skill]] for defuddle CLI details.
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.
- 7d ago First seen · 104 lines · 39 tokens per session scan A 6812d6f870ff
ingest-url is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 650 once invoked, about $0.0002 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-08-30.
Other commands, from other repositories
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
ingest
Ingest a source (URL/file/text) into Raw Sources + compile 1015 Wiki pages, with mandatory user-purpose gate and mothership cross-linking.
audit
Audit the whole Wiki vault against 3 knowledge-integrity criteria — eligibility coverage, MOC-cluster consistency, confidence calibration. Produces a vault health report and queues high-priority pages for /verify.
verify
Verify a single Wiki page against 3 knowledge-integrity criteria — eligibility, consistency, confirmability. Writes verificationStatus back to the page; flags conflicts as disputed rather than deleting them.
lint
Run comprehensive wiki health check — orphans, broken links, contradictions, stale pages, index sync, MOC coverage, v2/v4/v5 frontmatter coverage, Core Context freshness, and cross-vault link integrity (mainVaultRelated/mainVaultCmds).
capture-tabs
Capture a Chrome research tab group or AI-chat research session into LLM Wiki Inbox markdown, then optionally route it through /inbox or /ingest.