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 Knuckles-Team/freshrss-agent --skill freshrss-agent-developmentgit clone --depth 1 https://github.com/Knuckles-Team/freshrss-agentWrote 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/knuckles-team/freshrss-agent/freshrss-agent-development)<a href="https://agentmods.dev/skills/knuckles-team/freshrss-agent/freshrss-agent-development"><img src="https://agentmods.dev/badge/skills/knuckles-team/freshrss-agent/freshrss-agent-development/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/knuckles-team/freshrss-agent/freshrss-agent-development"><img src="https://agentmods.dev/badge/skills/knuckles-team/freshrss-agent/freshrss-agent-development.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.00052 | $0.01348 |
| Opus 5.5 | $0.00021 | $0.00539 |
| Sonnet 5.5 | $0.00010 | $0.00270 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
freshrss-agent-development 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 today.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
freshrss-agent development
This repository owns the FreshRSS Google Reader API facade, authentication
boundary, action-routed MCP tools, feed ontology and KG ingestion mappings, and
packaged connector content. Shared connector contracts, transports, TLS
profiles, and credential helpers belong to agent-connector-sdk; admission,
serving, and durable graph state belong to their owning repositories. Read
AGENTS.md before changing code and keep credentials, private endpoints,
tenant data, and customer records out of source, logs, fixtures, and skill
content.
Rapid delivery: the 5-minute contract
Specs are already designed. Deliver small, reviewable slices and cite the owning spec row in the commit trailer.
- Find the owning row first with
git grep -n "<term>" -- specsand extend the existing spec before adding requirement text. - Reuse the single
Connectorinfreshrss_agent/__init__.py, the facade infreshrss_agent/api_client.py, modular API clients underfreshrss_agent/api/, and action-routed tools infreshrss_agent/mcp/plusfreshrss_agent/mcp_server.py. Do not create a second API, MCP, authentication, or transport plane. - Preserve
FRESHRSS_URL,FRESHRSS_USER,FRESHRSS_API_PASSWORD,FRESHRSS_TLS_PROFILE, andFRESHRSS_TLS_PROFILE_REFhandling infreshrss_agent/auth.py. Keep the existing optional OIDC delegation path (ENABLE_DELEGATION) and SDK TLS resolution; never print credentials or add a verification bypass. - Keep the FreshRSS GReader API paths, cursor pagination, item normalization, subscription actions, and response models stable. Mock HTTP responses in tests; never call a live FreshRSS instance or use live credentials in a gate.
- Preserve best-effort typed/document KG ingestion in
freshrss_agent/kg_ingest.py, source declarations infreshrss_agent/connector_sources.py, and neutral ontology mappings. Do not bypass the sharedagent_connector_sdk.ingestfacade. - Keep
skills/**,ontology/**, prompts, andmcp_config.jsoncoherent with package data and theagent_connector_sdk.connectorentry point (freshrss-mcp = "freshrss_agent:connector"). Generatedspecs/*/status.jsonfiles come from shared hooks; never hand-edit them. - Every delivered requirement needs a bound focused test. This development
skill binds to the central criterion
PIPE-CONNSPEC-R122.4; it does not add a local status or rollup edit.
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.
- today First seen · 122 lines · 52 tokens per session scan A 9cf4999b1bf2
freshrss-agent-development is a skill published in the GitHub repository Knuckles-Team/freshrss-agent (0 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,348 once invoked, about $0.0002 per session on Opus 5.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-10-27.
Other skills, from other repositories
gitlab-api-development
Develop, test, gate, and release the GitLab REST and GraphQL connector. Use this skill when changing API mappings, governed MCP tools, authentication, tenant selection, KG ingestion, packaged content, or repository gates.
hdhomerun-mcp-development
Develop, test, gate, and release the HDHomeRun connector while preserving its local tuner and cloud DVR boundaries, SDK connector wiring, packaged content, and source-backed Pages publication.
servicenow-api-development
Develop, test, and publish the servicenow-api connector while preserving its typed ServiceNow clients, MCP surface, packaged content, spec evidence, and shared release gates.
epistemic-graph-development
Develop, build, test, and gate changes in the epistemic-graph engine repository. Use before adding a capability, changing the wire contract, or running the test/gate suite in this repo. Covers the Rust-native rule (new behaviour is a Rust crate exposed through the generated wire contract; Python/Go/JS are clients, not…
systems-manager-development
Develop, test, and release the systems-manager Python connector. Covers the cross-platform systems manager, governed FastMCP server, connector source declarations, packaged skills and ontology, documentation, and the repository's shared delivery gates. Use before changing a provider tool, MCP boundary, connector…
jellyfin-mcp-development
Develop and validate the jellyfin-mcp connector using its actual agent-connector-sdk entrypoint, Jellyfin API clients, ontology assets, packaged skills, and focused tests. Use this skill for source changes and delivery gates; use the provider skills for live Jellyfin operations.