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 Buzzmatic/awesome-agent-skills --skill dfs-technologiesgit clone --depth 1 https://github.com/Buzzmatic/awesome-agent-skillsWrote 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/buzzmatic/awesome-agent-skills/dfs-technologies)<a href="https://agentmods.dev/skills/buzzmatic/awesome-agent-skills/dfs-technologies"><img src="https://agentmods.dev/badge/skills/buzzmatic/awesome-agent-skills/dfs-technologies/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/buzzmatic/awesome-agent-skills/dfs-technologies"><img src="https://agentmods.dev/badge/skills/buzzmatic/awesome-agent-skills/dfs-technologies.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.00080 | $0.02624 |
| Opus 5 | $0.00040 | $0.01312 |
| Sonnet 5 | $0.00016 | $0.00525 |
| Haiku 4.5 | $0.00008 | $0.00262 |
Grade A, and why
dfs-technologies 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 8d 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DataForSEO Technologies API
Analyze technology usage across domains and discover domains using specific technologies.
Quick Start
# Find domains using WordPress
python scripts/domains_by_technology.py --technology "WordPress"
# Get technology stack for a domain
python scripts/domain_technologies.py --domain example.com
# Bulk technology analysis
python scripts/domain_technologies.py --bulk domains.txt
Available Scripts
| Script | Purpose |
|---|---|
domains_by_technology.py |
Search domains using specific technologies |
domain_technologies.py |
Get technology stack for domain(s) |
Domains by Technology (domains_by_technology.py)
Find domains based on their technology usage. Requires at least one technology selection parameter.
Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
--technology |
One of these | - | Technology name (repeatable, max 10) |
--group |
required | - | Technology group ID (repeatable, max 10) |
--category |
- | Technology category ID (repeatable, max 10) | |
--technology-path |
- | Technology path "$group.$category" (repeatable, max 10) | |
--keyword |
- | Keyword matching domain metadata (repeatable, max 10) | |
--mode |
No | as_is | Search mode: as_is (exact) or entry (partial) |
--filters |
No | - | JSON string or file with filter conditions |
--order-by |
No | - | Sort: field:asc or field:desc (repeatable, max 3) |
--limit |
No | 100 | Max results (max 10,000) |
--offset |
No | 0 | Pagination offset (max 9,999) |
--offset-token |
No | - | Pagination token for >100,000 results |
--tag |
No | - | Task identifier (max 255 chars) |
--output |
No | auto | Custom output path |
Examples
Find domains using WordPress:
python scripts/domains_by_technology.py --technology "WordPress"
Find domains using multiple technologies:
python scripts/domains_by_technology.py \
--technology "WordPress" \
--technology "WooCommerce"
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 375 lines · 0 tokens per session scan A 39ad39792697
dfs-technologies is a skill published in the GitHub repository Buzzmatic/awesome-agent-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 2,624 once invoked, about $0.0004 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-31.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…