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 S3YED/appie-kit --skill seo-technische-seogit clone --depth 1 https://github.com/S3YED/appie-kitWrote 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/s3yed/appie-kit/seo-technische-seo)<a href="https://agentmods.dev/skills/s3yed/appie-kit/seo-technische-seo"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/seo-technische-seo/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/s3yed/appie-kit/seo-technische-seo"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/seo-technische-seo.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.00031 | $0.01148 |
| Opus 5 | $0.00015 | $0.00574 |
| Sonnet 5 | $0.00006 | $0.00230 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
seo-technische-seo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Technische SEO Skill
Purpose
Ensure Google can crawl, index, and correctly interpret any Weblyfe site. Use this at site launch (prerequisite before any on-page or off-page work), when a site is not appearing in search results, or when rankings drop unexpectedly. Also covers rich markup (structured data) which unlocks enhanced SERP features.
Source
"Technische SEO" PDF from the source SEO course (downloaded from Drive 2026-05-03).
Quick reference
| Task | Action |
|---|---|
| Submit sitemap | Google Search Console > Sitemaps > add sitemap.xml URL |
| Find crawl errors | Google Search Console > Coverage > Errors |
| Check mobile rendering | Google Mobile-Friendly Test + manual device check |
| Add local business schema | Add LocalBusiness JSON-LD to homepage |
| Add product schema | Add Product JSON-LD with price, availability, reviews |
| Add review schema | Add AggregateRating JSON-LD |
| Speed check | Google PageSpeed Insights (mobile score is primary) |
| Validate structured data | Google Rich Results Test (search.google.com/test/rich-results) |
Core principles
- Schone code is the foundation. Google's crawler reads your HTML directly. Dirty, bloated, or broken code slows crawling and reduces indexing quality.
- Sitemaps tell Google what pages exist and which to prioritise. Submit XML sitemap via Search Console.
- Errors (4xx, 5xx) waste crawl budget and signal poor site health. Monitor and fix via Search Console > Coverage.
- Slechte software and poorly coded plugins add bloat, JavaScript errors, and slow load times. Each plugin is a liability.
- Mobile-first indexing is the current Google standard. The mobile version of a page is what Google indexes and ranks.
- Rich markup (structured data / schema.org) makes a site "semantisch" - Google understands entities, not just text. This unlocks rich snippets in SERPs.
- Rich markup types available for Weblyfe clients: Locatie (LocalBusiness), Producten (Product), Recepten (Recipe), Reviews (AggregateRating), Events, Vacatures (JobPosting), Website elementen (WebSite with Sitelinks search box).
- Fast indexing = competitive advantage for fresh content (news, events, pricing). Submit URLs via Search Console > URL Inspection > Request Indexing for time-sensitive pages.
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 · 84 lines · 31 tokens per session scan A 52db3060f8a3
seo-technische-seo is a skill published in the GitHub repository S3YED/appie-kit (9 stars, last pushed 17d ago), licensed MIT. It adds 31 tokens to every session and 1,148 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-09-03.
Other skills, from other repositories
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
content-distribution
Content distribution as a discipline. Owned channels (newsletter, blog, social), earned channels (PR, syndication, mentions), paid channels (boosted posts, syndication networks), and the channel-fit decisions that distinguish strategic distribution from spam-everywhere. Audience-channel matching, content-channel…
review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
agents-md-protocol
Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.
python-memory-safe-scripts
Memory-safe Python script patterns for long-running processes under systemd MemoryMax constraints. Covers allocator purge (mimalloc/glibc malloctrim), HTTP response lifecycle, DataFrame cleanup, thread-local connection reuse, and periodic GC cadence. Battle-tested through 5 OOM optimization cycles on production GPU…