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 skills add DavidROliverBA/ArchitectKB --skill weblinkgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/skills/davidroliverba/architectkb/weblink)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/weblink"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/weblink/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/weblink"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/weblink.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00600 |
| Opus 5 | $0.00000 | $0.00300 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
weblink 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 9d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/weblink
Save a URL as a weblink note with analysis and summary.
Usage
/weblink <url>
/weblink <url> <optional title>
Examples
/weblink https://github.com/anthropics/claude-code
/weblink https://aws.amazon.com/bedrock/ AWS Bedrock Service
Instructions
-
Fetch and analyse the URL:
- Use WebFetch to retrieve the page content
- Extract: title, author, source/domain, main content
- ALWAYS provide analysis - this is mandatory, not optional
-
Generate analysis (REQUIRED):
- Write a 2-3 sentence summary of what the resource is
- Extract 4-8 key points as bullet points
- Identify relevance to your organization/Solutions Architecture work where applicable
- Note any technical details (technologies, integrations, versions)
-
Generate filename:
Weblink - {{title}}.md -
Create weblink in vault root:
---
type: Weblink
title: {{title}}
created: {{DATE}}
modified: {{DATE}}
tags: [{{relevant tags}}]
url: {{url}}
domain: {{domain}}
author: {{author or null}}
source: {{source name}}
---
# {{title}}
## Source
- **URL:** {{url}}
- **Author:** {{author}}
- **Source:** {{source}}
## Summary
{{2-3 sentence summary of the resource}}
## Key Points
- {{key point 1}}
- {{key point 2}}
- {{key point 3}}
- {{...more as relevant}}
## Relevance to your organization
{{How this relates to YourOrg work, if applicable. Remove section if not relevant.}}
## Related
- {{wiki-links to related notes in vault}}
-
Tag extraction:
- Identify 2-5 relevant tags from content
- Use existing vault tags where possible (check other notes)
- Common tags: AWS, SAP, MCP, AI, architecture, integration, security
-
Find related notes:
- Search vault for related topics
- Add wiki-links to relevant existing notes
- Consider: projects, technologies, people, other weblinks
-
After creating:
- Confirm creation with file path
- Show brief summary of what was saved
- Mention key relevance if applicable
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.
- 9d ago First seen · 103 lines · 0 tokens per session scan A 711dab90072d
weblink is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 600 tokens. 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-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…