Install the "sync-upstream-radius" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/sync-upstream-radius into .claude/skills/sync-upstream-radius/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-upstream-radius", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add talkincode/toughradius --skill sync-upstream-radius -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "sync-upstream-radius" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/sync-upstream-radius into .agents/skills/sync-upstream-radius/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-upstream-radius", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add talkincode/toughradius --skill sync-upstream-radius -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "sync-upstream-radius" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/sync-upstream-radius into .cursor/skills/sync-upstream-radius/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-upstream-radius", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add talkincode/toughradius --skill sync-upstream-radius -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "sync-upstream-radius" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/sync-upstream-radius into .gemini/skills/sync-upstream-radius/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-upstream-radius", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add talkincode/toughradius --skill sync-upstream-radius -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "sync-upstream-radius" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/sync-upstream-radius into .github/skills/sync-upstream-radius/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-upstream-radius", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add talkincode/toughradius --skill sync-upstream-radius -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "sync-upstream-radius" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/sync-upstream-radius into .opencode/skills/sync-upstream-radius/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-upstream-radius", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
sync-upstream-radius
GitHub stars
691
Token cost
~736 tokens
SKILL.md length
297 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT
At a glance
Track and sync the upstream layeh.com/radius library to the org fork talkincode/radius (TR-F021/TR-F022).
Works in 5 steps: Confirm the currently pinned version → Diff against upstream → Assess the sync → …
A check finds new upstream commits
SKILL.md covers Background, When to use, Steps and Boundaries, plus 1 more section
Calls go and git; reaches github.com
What it does
Sync Upstream Radius is an agent skill from talkincode/toughradius. Track and sync the upstream layeh.com/radius library to the org fork talkincode/radius (TR-F021/TR-F022). Use when a check finds new upstream commits, a protocol-library defect is suspected, or for routine dependency maintenance.
Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Go. The repository describes itself as: A powerful, open-source RADIUS server designed for ISPs, enterprise networks, and carriers. Supports standard RADIUS protocols, a full EAP / 802.1X authentication suite (EAP-TLS… The licence is MIT.
When your agent uses it
A check finds new upstream commits
A protocol-library defect is suspected
For routine dependency maintenance
Example prompts
“/sync-upstream-radius”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
1Confirm the currently pinned version
2Diff against upstream
3Assess the sync
4Verify
5Regression protection: if the sync fixes a protocol defect, add a test that reproduces it to prevent future regressions.
What it can do on your machine
Read from SKILL.md and the folder at commit 50907c9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
go
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sync Upstream Radius loads about 736 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 297 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~63
When it runs· the whole SKILL.md, loaded when a task matches
~736
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/sync-upstream-radius/SKILL.md (or your agent's skills folder).
name
sync-upstream-radius
description
Track and sync the upstream layeh.com/radius library to the org fork talkincode/radius (TR-F021/TR-F022). Use when a check finds new upstream commits, a protocol-library defect is suspected, or for routine dependency maintenance.
Record the fork tag the replace points to, and the upstream commit short SHA in the require pseudo-version.
Diff against upstream
Original repo layeh/radius: review new commits since the pinned commit, e.g. via GitHub compare:
https://github.com/layeh/radius/compare/<pinned_sha>...master, or git log <pinned_sha>.. in an upstream clone.
Focus on: security fixes, attribute codec correctness, EAP / VSA / packet-parsing changes.
Assess the sync
If an upstream fix is important and the fork lacks it: merge/cherry-pick it into the fork (talkincode/radius) and cut a new tag.
Update this repo's go.modreplace to the new tag and run go mod tidy.
If the fix does not affect this project's usage, record the "assessed, sync deferred" rationale (reply in the tracking issue).
Verifybash
go build ./...
go test ./...
go test -tags=integration -count=1 ./test/integration/... # needs Postgres, see ../add-acceptance-test/SKILL.md
golangci-lint run
Regression protection: if the sync fixes a protocol defect, add a test that reproduces it to prevent future regressions.
Boundaries
Do not vendor or patch third-party library source directly in this repo; changes go through the fork repo.
replace points only to the trusted org fork; do not introduce unknown third-party branches.
Upgrades must be explained in the PR: upstream commit range, risk assessment, and whether protocol behavior is affected.
Acceptance
go.mod / go.sum are consistent, go mod tidy leaves no residue
Full + integration tests pass
The tracking issue records the sync decision (sync / defer + rationale)
Sync Upstream Radius next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Sync Upstream Radius compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Sync Upstream Radius this skilltalkincode/toughradius
Walks through adding a new Redis or Redis module command to the go-redis client, from fetching the spec and docs to the type, interface wiring, parsing and tests.
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
Prepare an Apache Fory release candidate from a clean release branch, including the version bump, RC tag, JVM staging, ASF source artifacts, SVN upload, and vote email.
Launches, restarts and troubleshoots the real AO Electron desktop app from a checkout, with isolated or real local data and checks for stale processes.
Starts a Dozzle dev server on a port derived from the current worktree so you can test by hand in a browser, without disturbing instances started elsewhere.
Track and sync the upstream layeh.com/radius library to the org fork talkincode/radius (TR-F021/TR-F022). Sync Upstream Radius is an agent skill from talkincode/toughradius.com/radius library to the org fork talkincode/radius (TR-F021/TR-F022).
When should I use Sync Upstream Radius?
Sync Upstream Radius fits situations like: A check finds new upstream commits; A protocol-library defect is suspected; for routine dependency maintenance.
How do I install Sync Upstream Radius in Claude Code?
Run `npx skills add talkincode/toughradius --skill sync-upstream-radius -a claude-code`. Or copy the skill folder (.agents/skills/sync-upstream-radius in talkincode/toughradius) into .claude/skills/sync-upstream-radius in your project. Claude Code loads it when a task matches its description.
How do I install Sync Upstream Radius in Codex?
Run `npx skills add talkincode/toughradius --skill sync-upstream-radius -a codex`. Or copy the skill folder (.agents/skills/sync-upstream-radius in talkincode/toughradius) into .agents/skills/sync-upstream-radius in your project. Codex loads it when a task matches its description.
Can I use Sync Upstream Radius in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add talkincode/toughradius --skill sync-upstream-radius -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sync-upstream-radius, .gemini/skills/sync-upstream-radius, .github/skills/sync-upstream-radius and .opencode/skills/sync-upstream-radius in your project.
What does Sync Upstream Radius need to run?
Going by SKILL.md and its folder, Sync Upstream Radius needs the command-line tools its instructions call (go and git).
Does Sync Upstream Radius access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Sync Upstream Radius safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sync Upstream Radius use?
Sync Upstream Radius is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sync Upstream Radius use?
About 736 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sync Upstream Radius?
Skills that share tags, products or a category with Sync Upstream Radius: Add Redis Command to go-redis (redis/go-redis, 22k stars), Go Pedantry (chromedp/chromedp, 13k stars), Fory Release (apache/fory, 4.6k stars) and AO Desktop App Launcher (OrchestratorInc/agent-orchestrator, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sync Upstream Radius?
talkincode (a GitHub organization) maintains it in talkincode/toughradius, which has 691 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 3, 2026.
Source: talkincode/toughradius on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
