agentmods.dev

sitemap

Instructions for serving an XML sitemap and robots.txt in a Phoenix application. An XML sitemap is a list of public pages that search engines can discover.

In plain words
What is it for?
Use it to add static or dynamic URLs to a sitemap and point robots.txt to that sitemap.
Why use it?
It helps search engines find indexable pages through standard endpoints and requires no extra dependency. It is not intended for private applications with no public pages.

Skill for Claude CodeCodex

2 2mo ago A scan 39 tokens original MIT
View the source file fullstack-phoenix/saas_kit
Install

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.

agentmods
npx agentmods add skills/fullstack-phoenix/saas_kit/sitemap
Any agent
npx skills add fullstack-phoenix/saas_kit --skill sitemap
Clone the repo
git clone --depth 1 https://github.com/fullstack-phoenix/saas_kit

Made for: Claude Code, Codex.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 954 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.00954
Opus 5 $0.00019 $0.00477
Sonnet 5 $0.00008 $0.00191
Haiku 4.5 $0.00004 $0.00095

Measured yesterday against content hash 23a258064114, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sitemap 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 yesterday.

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.

skills/sitemap/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

XML Sitemaps

Serves an XML sitemap at /sitemap.xml using a plain Phoenix controller and an EEx template, and wires robots.txt to point at it. No external dependencies — it adds the :xml format to the web entrypoint, a route, a SitemapController, a SitemapXML view, and the template you edit to list your URLs.

When to use

  • The app is public and you want search engines to discover its pages.
  • You need a standards-compliant (sitemaps.org) sitemap served with the correct XML content type.
  • Don't bother for an internal/admin-only app with no indexable public pages.

Dependencies

  • Requires: None.
  • Recommended: None.

Install

mix saaskit.feature.install sitemap

No installer decisions. It injects the :xml format and route, appends the Sitemap: line to robots.txt, and generates the controller, view, template, and test.

What it generates

  • lib/my_app_web/controllers/sitemap_controller.ex — index/2 renders index.xml with layout: false and text/xml content type.
  • lib/my_app_web/controllers/sitemap_xml.ex — SitemapXML view using embed_templates "sitemap_xml/*".
  • lib/my_app_web/controllers/sitemap_xml/index.xml.eex — the sitemap template (one <url> entry for / by default).
  • test/my_app_web/controllers/sitemap_controller_test.exs — asserts the route returns XML.
  • Adds :xml to the allowed formats in lib/my_app_web.ex.
  • Adds get "/sitemap.xml", SitemapController, :index to lib/my_app_web/router.ex.
  • Appends Sitemap: https://example.com/sitemap.xml to priv/static/robots.txt.

Configuration

No config keys. The only value to change is the domain in priv/static/robots.txt:

Sitemap: https://example.com/sitemap.xml

Replace example.com with your production domain.

Tweaking for your app

Add static routes to the template:

<%# lib/my_app_web/controllers/sitemap_xml/index.xml.eex %>
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="https://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc><%= url(~p"/") %></loc>
    <changefreq>daily</changefreq>
    <priority>1</priority>
  </url>
  <url>
    <loc><%= url(~p"/pricing") %></loc>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Read the full file on GitHub · 112 lines

Changes

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.

  1. yesterday First seen · 112 lines · 39 tokens per session scan A 23a258064114

Subscribe to this mod's changes

sitemap is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 954 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-31.

Research
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens