SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Slipmark 0.6 adds MCP server to bind Codex review verdicts to their instruction files

0
·2 views

Slipmark 0.6 introduces an MCP server for Codex, motivated by the fact that coding agents read AGENTS.md, skills, and MCP configuration as inputs, which became targets of 2026 attacks such as Ghostcommit, Deadbugz, and poisoned skills. The server gives Codex two tools: slipmark_attest, which records a verdict along with SHA-256 hashes of the files read, and slipmark_verify, which checks those verdicts against the current file contents. A companion CI action blocks pull requests when files or agent instructions changed after a verdict, or when AGENTS.md changed without human approval or instructions hid text from reviewers. The MCP server is intentionally limited: agents cannot record human approvals, run commands, or overwrite existing verdicts. A demo repository presents each attack as an open pull request.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

DeadNet Browser Uses AI to Revive Decaying 1990s and 2000s Websites

DeadNet Ectoplasm Browser is an open-source project that uses AI to exhume late-1990s and early-2000s websites that have decayed or vanished from the web. Many of these sites are lost to link rot, with missing stylesheets, broken images, and defunct server-side scripts. The tool diagnoses broken pages, repairs dead assets, and converts old CGI scripts into working client-side code. Users can move a time-travel slider to view a site in its original 1998 style, an annotated mode, or a modernized 2026 version. The project is built on open-weight Gemma 3 models and was submitted to a Hacktoberfest AI challenge.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Google Trends US data shows a distorted spike in spring 2026, affecting seasonality and trend analysis

A developer building a niche report found that US Google Trends data for shopping searches shows an unusual spike between March and July 2026. Searches that have no connection to each other, such as headphones and mechanical keyboards, rose in the same weeks and fell back by mid-July, suggesting a data problem rather than real consumer interest. The regional pattern also looks implausible, with Wyoming showing a sudden burst that makes it the top state for many unrelated keywords. The author warns that metrics like seasonality, trend direction and momentum computed over that window can be misleading. Year-over-year comparisons outside the affected weeks are generally unaffected, and the author suggests checking unrelated keywords and excluding the distorted weeks.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Form submissions need an uncertain state when the server response is lost

A browser form can send an enquiry that the server saves while the response never reaches the page, leaving the interface unsure whether it succeeded. The article argues that displaying a generic failure message asserts something the browser cannot know, and that disabling buttons does not prevent duplicate server-side work. It describes a four-state controller (ready, sending, received, uncertain) that only treats a response as received when the HTTP status is successful, the JSON body confirms success, and a UUID-shaped reference is present. Ambiguous outcomes such as lost connections or malformed responses enter the uncertain state, where the page avoids automatic resending and offers an alternative contact route. The author notes that this approach is conservative, is not an exactly-once guarantee, and that endpoints supporting idempotency keys should follow their own documented contracts.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Beginner's Guide Explains How CSS Controls Webpage Layout

A DEV Community article introduces CSS as the tool that determines how webpage elements are positioned, aligned, and spaced, not just how they look. It explains that CSS layout decides whether elements stack vertically or sit side by side, how much room they occupy, and how they adapt on smaller screens. The guide focuses on the display property and covers the core values block, inline, and inline-block. It also previews more advanced layout systems such as flex and grid for beginners learning web design.

0 comments Read more at DEV Community